AspectJ Maven Plugin

<additionalCompilerArgs>
  <arg>-Xmaxerrs=1000</arg>
  <arg>-Xlint</arg>
  <arg>-J-Duser.language=en_us</arg>
</additionalCompilerArgs>

Caveat: Be careful when using this option and select the additional compiler arguments wisely, because behaviour is undefined if you add arguments which have already been added by the plugin using regular parameters or their default values. The resulting compiler command line will in that case contain duplicate arguments, which might be illegal depending on the specific argument. Do not expect to be able to manually override existing arguments using this option or to replace whole argument lists.

For reproducible builds, please change the directory to be outside the outputDirectory, because argument files contain path names, which can vary between build systems. So you do not want an argument file to end up in your build artifact (e.g. JAR file) for a reproducible build.

Caveat: If you configure a common directory, e.g. ${project.build.directory}/aj-build, in the plugin configuration, please make sure to choose different argumentFileNames for compile vs test-compile goal execution configurations to avoid one file overwriting the other.

By default, the file will be placed in the respective build output directory, i.e. in the same directory where your application or test classes reside, and will contain all the arguments passed to the AJC compiler in the last run, and also all the files included in the AJC build. The file is also used to determine if recompilation is necessary in subsequent builds. The argumentFileDirectory can be changed, which is helpful for reproducible builds.

A typical builddef.lst file might look like this:

-1.8
-encoding
UTF-8
-classpath
/my/library/lib.jar:/somewhere/aspectjrt.jar:/my/project/target/classes
-d
/my/project/target/classes
/my/project/src/main/java/org/acme/ValidationAspect.java

Using this option overrides source, target. If you want the latter two to be different, make sure not to use this option.

Please note: You cannot run code compiled with preview features on any other JDK than the one used for compilation. For example, records compiled with preview on JDK 15 cannot be used on JDK 16 without recompilation. This is a JVM limitation unrelated to AspectJ. Also, e.g. sealed classes are preview-1 on JDK 15 and preview-2 on JDK 16. You still need to recompile, no matter what.

Using this option overrides all of complianceLevel, source, target. Please note that before AspectJ 1.9.8.M1, the --release N compiler option was not working correctly.

See AjcHelper.isValidComplianceLevel(java.lang.String) for details about valid version numbers in general, but please note that permitted version numbers for this option depend on the JDK used for compilation, as more recent JDKs might drop cross-compilation support for older ones.

If unspecified, the AspectJ compiler's default (1.4 for AspectJ 1.9.7) is used. Please note, that target defaults to the value set here.

Set the java source folders to use, specifying the includes and excludes.

If you don't specify this parameter, all java sources of the current project will be used. If you specify this parameter as an empty tag (i.e. <sources/>), all source folders will be ignored. Otherwise specify the source folder(s) to use.

If unspecified, this value defaults to source. If neither source nor target are specified, the AspectJ compiler's default is used.

constructorName

method with constructor name

packageDefaultMethod

attempt to override package-default method

deprecation

usage of deprecated type or member

maskedCatchBlocks

hidden catch block

unusedLocals

local variable never read

unusedArguments

method argument never read

unusedImports

import statement not used by code in file

none

suppress all compiler warnings