<plugin>
<groupId>org.apache.maven.plugins</groupId>
@@ -191,12 +189,13 @@ then additional transformers must be configured as part of the maven-shade-plugi
diff --git a/spring-cloud-function/3.0.0.M1/aws.html b/spring-cloud-function/3.0.0.M1/aws.html index 35394982..6d02dd3f 100644 --- a/spring-cloud-function/3.0.0.M1/aws.html +++ b/spring-cloud-function/3.0.0.M1/aws.html @@ -91,12 +91,10 @@ $(addBlockSwitches);
aws
-classifier for deploying in Lambda, and one executable (thin) jar that includes spring-cloud-function-web
+classifier for deploying in Lambda, and one executable (thin) jar that includes spring-cloud-function-web
at runtime. Spring Cloud Function will try and locate a "main class" for you from the JAR file
manifest, using the Start-Class attribute (which will be added for you by the Spring Boot
tooling if you use the starter parent). If there is no Start-Class in your manifest you can
@@ -157,7 +155,7 @@ use an environment variable or system property MAIN_CLASS when you
If you are not using the functional bean definitions but relying on Spring Boot’s auto-configuration, then additional transformers must be configured as part of the maven-shade-plugin execution.
-<plugin>
<groupId>org.apache.maven.plugins</groupId>
@@ -191,12 +189,13 @@ then additional transformers must be configured as part of the maven-shade-plugi
In order to run Spring Cloud Function applications on AWS Lambda, you can leverage Maven or Gradle plugins offered by the cloud platform provider.
In order to use the adapter plugin for Maven, add the plugin dependency to your pom.xml
file: