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 Total number of occurrences
@todo 13

Each tag is detailed below:


Number of occurrences found in the code: 13

org.apache.maven.artifact.Artifact Line
do we really need an interface here? 38
get rid of the multiple states we can have (project, parent, etc artifacts, file == null, snapshot, etc) - construct subclasses and use accordingly? 39
would like to get rid of this - or at least only have one. Base version should be immutable. 96
remove, a quick hack for the lifecycle executor 159
org.apache.maven.artifact.DefaultArtifact Line
this should possibly be replaced by type handler 42
should be final 54
org.apache.maven.artifact.DependencyResolutionRequiredException Line
it may be better for artifact.getFile() to throw it - perhaps it is a runtime exception? 27
org.apache.maven.artifact.metadata.ArtifactMetadata Line
merge with artifactmetadatasource 30
retrieval exception not appropriate for store 31
this should only be needed on the repository metadata 72
this should only be needed on the repository metadata 81
org.apache.maven.artifact.resolver.ArtifactResolver Line
possibly fix the signatures, it's unfortunate that in some methods the local repo is listed first and second in others. 38
org.apache.maven.artifact.resolver.filter.ExcludesArtifactFilter Line
I think this is equiv. to exclusion set filter in maven-core 31


Number of occurrences found in the code: 22

org.apache.maven.artifact.Artifact Line
into scope handler 50
org.apache.maven.artifact.factory.ArtifactFactory Line
deprecate and chase down (probably used for copying only) 29
org.apache.maven.artifact.factory.DefaultArtifactFactory Line
remove, it doesn't know the ones from the plugins 31
can refactor - inherited scope calculation belongs in the collector, use scope handler 123
org.apache.maven.artifact.resolver.DefaultArtifactCollector Line
we probably want to warn the user that he is building an artifact with different values than in dependencyManagement 130
Does this check need to happen here? Had to add the same call below when we iterate on child nodes -- will that suffice? 152
shouldn't need to double up on this work, only done for simplicity of handling recommended version but the restriction is identical 174
ick. this forces the OCE that should have come from the previous call. It is still correct 177
use as conflict resolver(s), chain 239
should this be part of mediation? previous one is more dominant 241
maybe its better to just pass the range through to retrieval and use a transformation? 342
might be better to have source.retrieve() throw a specific exception for this situation and catch here rather than have it return null 409
org.apache.maven.artifact.resolver.DefaultArtifactCollectorTest Line
use newest conflict resolver 156
use newest conflict resolver 176
org.apache.maven.artifact.resolver.ResolutionListener Line
Use the following two instead of manageArtifact 85
Remove ResolutionListenerDM interface 86
org.apache.maven.artifact.resolver.ResolutionNode Line
if it was null, we really need to go find them now... or is this taken care of by the ordering? 200
org.apache.maven.artifact.resolver.filter.IncludesArtifactFilter Line
what about wildcards? Just specifying groups? versions? 50
org.apache.maven.artifact.versioning.VersionRange Line
should throw this immediately, but need artifact 297
could be more efficient by sorting the list and then moving along the restrictions in order? 520
org.apache.maven.artifact.versioning.VersionRangeTest Line
current policy is to retain the original version - is this correct, do we need strategies or is that handled elsewhere? assertEquals( CHECK_VERSION_RECOMMENDATION, "1.1", mergedRange.getRecommendedVersion().toString() ); 173
test reversed restrictions on all below 194