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 | 4 | @deprecated |
| FIXME Work | 0 | fixme, @fixme |
| Todo Work | 10 | todo, @todo |
Each tag is detailed below:
Deprecated Work
Number of occurrences found in the code: 4
| org.apache.maven.plugins.javadoc.AbstractJavadocMojo | Line |
|---|---|
| This is no longer evaluated, instead use {@link #addStylesheets} to customize the CSS. | 1264 |
| if these sources depend on transitive dependencies, those dependencies should be added to the pom as direct dependencies | 1501 |
| org.apache.maven.plugins.javadoc.JavadocJar | Line |
| --No comment-- | 100 |
| org.apache.maven.plugins.javadoc.JavadocVersion | Line |
| Use {@link org.codehaus.plexus.languages.java.version.JavaVersion} instead | 30 |
Todo Work
Number of occurrences found in the code: 10
| org.apache.maven.plugins.javadoc.AbstractFixJavadocMojo | Line |
|---|---|
| check algo, seems broken (only takes in account the last param) | 2359 |
| org.apache.maven.plugins.javadoc.AbstractJavadocMojo | Line |
| remove the part with ToolchainManager lookup once we depend on 3.0.9 (have it as prerequisite). Define as regular component field then. | 2608 |
| --No comment-- | 4522 |
| Why are we only interested in cases where the JVM won't start? [MJAVADOC-275][jdcasey] I changed the logic here to only throw an error WHEN the JVM won't start (opposite of what it was). | 5540 |
| only copy when changed | 5735 |
| org.apache.maven.plugins.javadoc.JavadocJar | Line |
| these introduced dependencies on the project are going to become problematic - can we export it through metadata instead? | 195 |
| org.apache.maven.plugins.javadoc.JavadocReport | Line |
| Replace null with real value | 299 |
| org.apache.maven.plugins.javadoc.JavadocReportTest | Line |
| This got disabled for now! This test fails since the last commit but I actually think it only ever worked by accident. It did rely on a commons-logging-1.0.4.pom which got resolved by a test which did run previously. But after updating to commons-logging.1.1.1 there is no pre-resolved artifact available in target/local-repo anymore, thus the javadoc link info cannot get built and the test fails I'll for now just disable this line of code, because the test as far as I can see _never_ did go upstream. The remoteRepository list used is always empty!. | 973 |
| org.apache.maven.plugins.javadoc.JavadocUtil | Line |
| deprecate in favor of Path.relativize | 1245 |
| org.apache.maven.plugins.javadoc.TestJavadocReport | Line |
| the prerequisite is that the main report is in apidocs | 301 |