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 | 9 | @deprecated |
FIXME Work | 0 | fixme, @fixme |
Todo Work | 9 | todo, @todo |
Each tag is detailed below:
Number of occurrences found in the code: 9
org.apache.maven.plugin.AbstractMojo | Line |
---|---|
Use SLF4J directly | 147 |
Use SLF4J directly | 167 |
org.apache.maven.plugin.Mojo | Line |
Use SLF4J directly | 54 |
Use SLF4J directly | 64 |
org.apache.maven.plugin.descriptor.PluginDescriptorBuilder | Line |
use {@link #build(ReaderSupplier)} | 62 |
use {@link #build(ReaderSupplier, String)} | 70 |
use {@link #build(StreamSupplier, String)} | 97 |
org.apache.maven.plugin.logging.Log | Line |
Use SLF4J directly | 30 |
org.apache.maven.plugin.logging.SystemStreamLog | Line |
Use SLF4J directly | 28 |
Number of occurrences found in the code: 9
org.apache.maven.plugin.descriptor.MojoDescriptor | Line |
---|---|
is there a need for the delegation of MavenMojoDescriptor to this? Why not just extend ComponentDescriptor here? | 39 |
the name is not intelligible | 275 |
org.apache.maven.plugin.descriptor.PluginDescriptor | Line |
v4 | 142 |
v4 | 149 |
v4 | 150 |
move to plugin-tools-api as a default only | 230 |
could we use a map? Maybe if the parent did that for components too, as this is too vulnerable to changes above not being propagated to the map | 328 |
org.apache.maven.plugin.descriptor.PluginDescriptorBuilder | Line |
this should not need to be handed off... | 450 |
org.apache.maven.plugin.logging.SystemStreamLog | Line |
Not sure how best to set these for this implementation... | 131 |