Fork me on GitHub

Tag List Report

The following document contains the listing of user tags found in the code. Below is the summary of the occurrences per tag.

Tag Class Total number of occurrences Tag strings used by tag class
Deprecated Work 38 @deprecated
FIXME Work 0 fixme, @fixme
Todo Work 11 todo, @todo

Each tag is detailed below:

Deprecated Work

Number of occurrences found in the code: 38

org.apache.maven.plugin.compiler.AbstractCompilerMojo Line
Replaced by the project-wide {@code <sources>} element. 258
Use {@link #compilerArgs} instead. 301
Replaced by ordinary dependencies with {@code <type>} element set to {@code processor}, {@code classpath-processor} or {@code modular-processor}. 389
This flag is ignored. Replaced by ordinary dependencies with {@code <type>} element set to {@code processor}, {@code classpath-processor} or {@code modular-processor}. 407
Setting this flag to {@code false} is replaced by {@code <debuglevel>none</debuglevel>}. 467
This property is ignored. 496
Bundling many class files into a single file should be done by other plugins. 568
Not used by the compiler plugin since it does not generate archive. 581
Replaced by {@link #incrementalCompilation}. A value of {@code true} in this old property is equivalent to {@code "dependencies,sources,rebuild-on-add"} in the new property, and a value of {@code false} is equivalent to {@code "classes"}. 666
This parameter is no longer used by the underlying compilers. 795
Ignored because the compiler plugin now always use the {@code javax.tools} API. 810
Ignored because {@code java.lang.Compiler} has been deprecated and removed from the JDK. 821
Not supported anymore. The reuse of {@link JavaFileManager} instance is plugin implementation details. 840
Deprecated as a consequence of {@link #compilerReuseStrategy} deprecation. 849
For compatibility with the previous way to build multi-release JAR file. May be removed after we drop support of the old way to do multi-release. 1093
This is invoked only by other deprecated methods. 1527
Replaced by ordinary dependencies with {@code <type>} element set to {@code processor}, {@code classpath-processor} or {@code modular-processor}. 1620
org.apache.maven.plugin.compiler.CompilerMojo Line
Replaced by specifying the {@code <targetVersion>} value inside a {@code <source>} element. 128
For compatibility with the previous way to build multi-release JAR file. May be removed after we drop support of the old way to do multi-release. 171
For compatibility with the previous way to build multi-release JAR file. May be removed after we drop support of the old way to do multi-release. 313
For compatibility with the previous way to build multi-release JAR file. May be removed after we drop support of the old way to do multi-release. 340
For compatibility with the previous way to build multi-release JAR file. May be removed after we drop support of the old way to do multi-release. 382
For compatibility with the previous way to build multi-release JAR file. May be removed after we drop support of the old way to do multi-release. 444
org.apache.maven.plugin.compiler.DependencyCoordinate Line
Used for {@link AbstractCompilerMojo#annotationProcessorPaths}, which is deprecated. 40
org.apache.maven.plugin.compiler.DependencyExclusion Line
Used for {@link AbstractCompilerMojo#annotationProcessorPaths}, which is deprecated. 26
org.apache.maven.plugin.compiler.DirectoryHierarchy Line
Used only for compatibility with Maven 3. 50
org.apache.maven.plugin.compiler.Options Line
Use {@link #addUnchecked(List)} instead. This method does not check for quoted strings. 367
org.apache.maven.plugin.compiler.TestCompilerMojo Line
Replaced by {@link #testCompilerArgs} for consistency with the main phase. 140
Use {@link #testCompilerArgs} instead. 153
Use {@code "claspath-jar"} dependency type instead, and avoid {@code module-info.java} in tests. 190
Avoid {@code module-info.java} in tests. 205
Declare modules in {@code <source>} elements instead. 370
org.apache.maven.plugin.compiler.ToolExecutor Line
Declare modules in {@code <source>} elements instead. 331
org.apache.maven.plugin.compiler.ToolExecutorForTest Line
Use {@code "claspath-jar"} dependency type instead, and avoid {@code module-info.java} in tests. 75
Avoid {@code module-info.java} in tests. 87
Declare modules in {@code <source>} elements instead. 101
Exists only for compatibility with the Maven 3 way to do a modular project. Is likely to cause confusion, for example with incremental builds. New projects should use the {@code <source>} elements instead. 118
This information exists only for compatibility with the Maven 3 way to build a modular project. 438

Todo Work

Number of occurrences found in the code: 11

org.apache.maven.plugin.compiler.AbstractCompilerMojo Line
consider making configurable. 104
Rename with a name making clearer that this parameter is about incremental build. 716
somehow shaky dependency between compilerId and tool executable. 1274
org.apache.maven.plugin.compiler.DirectoryHierarchy Line
use Path.resolve(String, String...) with Java 22. 90
replace by runtimeVersion() in Java 18. 111
org.apache.maven.plugin.compiler.PathSelector Line
use `LinkedHashSet.newLinkedHashSet(int)` instead with JDK19. 326
use `LinkedHashSet.newLinkedHashSet(int)` instead with JDK19. 425
org.apache.maven.plugin.compiler.SourceDirectory Line
Replace by return SourceVersion.valueOf(v) after upgrade to Java 18. 240
we could make this method non-static and verify that the given file is in the root of this directory. 321
org.apache.maven.plugin.compiler.SourceFile Line
compare with the file given by the compiler (if we can get that information) and set a `isStandardOutputFile` flag with the comparison result. 120
org.apache.maven.plugin.compiler.ToolExecutorForTest Line
replace by Path.resolve(String, String...) with JDK22. 374