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 | 6 | @deprecated |
| FIXME Work | 0 | fixme, @fixme |
| Todo Work | 9 | todo, @todo |
Each tag is detailed below:
Deprecated Work
Number of occurrences found in the code: 6
| org.apache.maven.plugin.javadoc.AbstractJavadocMojo | Line |
|---|---|
| since 2.5. Use the goals <code>javadoc:aggregate</code> and <code>javadoc:test-aggregate</code> instead. | 444 |
| since 2.4. Instead of, configure an active proxy host in <code>settings.xml</code>. | 823 |
| since 2.4. Instead of, configure an active proxy port in <code>settings.xml</code>. | 834 |
| org.apache.maven.plugin.javadoc.JavadocJar | Line |
| --No comment-- | 101 |
| org.apache.maven.plugin.javadoc.JavadocUtil | Line |
| since 2.5, using {@link #getCompileArtifacts(Set, boolean)} instead of. | 216 |
| since 2.5, using {@link #copyJavadocResources(File, File, String)} instead of. | 335 |
Todo Work
Number of occurrences found in the code: 9
| org.apache.maven.plugin.javadoc.AbstractFixJavadocMojo | Line |
|---|---|
| check algo, seems broken (only takes in account the last param) | 2727 |
| org.apache.maven.plugin.javadoc.AbstractJavadocMojo | Line |
| remove the part with ToolchainManager lookup once we depend on 2.0.9 (have it as prerequisite). Define as regular component field then. | 2671 |
| 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). | 5522 |
| org.apache.maven.plugin.javadoc.JavadocJar | Line |
| these introduced dependencies on the project are going to become problematic - can we export it through metadata instead? | 211 |
| org.apache.maven.plugin.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!. | 847 |
| org.apache.maven.plugin.javadoc.JavadocUtil | Line |
| classpath check doesn't belong here - that's the other method | 235 |
| let the scope handler deal with this | 238 |
| move to plexus-utils or use something appropriate from there | 1635 |
| org.apache.maven.plugin.javadoc.TestJavadocReport | Line |
| the prerequisite is that the main report is in apidocs | 339 |