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 ClassTotal number of occurrencesTag strings used by tag class

Each tag is detailed below:


Number of occurrences found in the code: 1

Fix: the class-use of the deprecated api is still created eventhough the deprecated api of that class is no longer generated295


Number of occurrences found in the code: 8

remove the part with ToolchainManager lookup once we depend on 2.0.9 (have it as prerequisite). Define as regular component field then.2533
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).5352
these introduced dependencies on the project are going to become problematic - can we export it through metadata instead?191
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!.829
classpath check doesn't belong here - that's the other method225
let the scope handler deal with this228
move to plexus-utils or use something appropriate from there1591
the prerequisite is that the main report is in apidocs336