As indicated above, this plugin adds basic building blocks for working with JVM projects.Its feature set has been superseded by other plugins, offering more features based on your project type.Instead of applying it directly to your project, you should look into the java-library or application plugins or one of the supported alternative JVM language.
The resources of this source set. Contains only resources, and excludes any .java files found in the resource directories. Other plugins, such as the Groovy Plugin, exclude additional types of files from this collection.
Using a custom executable or javaHome deactivates some optimizations.The compile task does not use incremental build immediately after a compile error or if a Java constant changes.Use toolchains instead if possible.
As a user you can see which annotation processors are triggering full recompilations in the --info log.Incremental annotation processing will be deactivated if a custom executable or javaHome is configured on the compile task.
If you use the appender library (aws-lambda-java-log4j2), you must also configure a transformer for the Maven Shade plugin. The transformer library combines versions of a cache file that appear in both the appender library and in Log4j.
At runtime, config vars are exposed to your app as environment variables. For example, modify GettingStartedApplication.java so that the method obtains an energy value from the ENERGY environment variable:
760c119bf3