Contents
-
Terminally Deprecated Elements
Not supported anymore. The reuse of
JavaFileManager instance is plugin implementation details.
This parameter is no longer used by the underlying compilers.
Ignored because java.lang.Compiler has been deprecated and removed from the JDK.
Ignored because the compiler plugin now always use the javax.tools API.
This property is ignored.
Bundling many class files into a single file should be done by other plugins.
Not used by the compiler plugin since it does not generate archive.
-
Deprecated Fields
Replaced by ordinary dependencies with <type> element set to
processor, classpath-processor or modular-processor.
This flag is ignored.
Replaced by ordinary dependencies with <type> element set to
processor, classpath-processor or modular-processor.
Not supported anymore. The reuse of
JavaFileManager instance is plugin implementation details.
This parameter is no longer used by the underlying compilers.
Replaced by the project-wide <sources> element.
Setting this flag to false is replaced by <debuglevel>none</debuglevel>.
Ignored because java.lang.Compiler has been deprecated and removed from the JDK.
Ignored because the compiler plugin now always use the javax.tools API.
This property is ignored.
Bundling many class files into a single file should be done by other plugins.
Not used by the compiler plugin since it does not generate archive.
Replaced by
AbstractCompilerMojo.incrementalCompilation.
A value of
true in this old property is equivalent to
"dependencies,sources,rebuild-on-add"
in the new property, and a value of
false is equivalent to
"classes".
Replaced by specifying the <targetVersion> value inside a <source> element.
Use "claspath-jar" dependency type instead, and avoid module-info.java in tests.