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
@todo 7 @todo

Each tag is detailed below:


Number of occurrences found in the code: 7

org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager Line
share with DefaultPluginMappingManager. 306
org.apache.maven.artifact.repository.metadata.SnapshotArtifactRepositoryMetadata Line
split instantiation (versioning, plugin mappings) from definition 29
org.apache.maven.project.interpolation.AbstractStringBasedModelInterpolator Line
Consolidate this logic with the PluginParameterExpressionEvaluator, minus deprecations/bans. 61
Remove the throws clause. 106
org.apache.maven.project.interpolation.RegexBasedModelInterpolator Line
Consolidate this logic with the PluginParameterExpressionEvaluator, minus deprecations/bans. 33
org.apache.maven.repository.legacy.resolver.conflict.DefaultConflictResolverFactory Line
you don't need the container in here with the active maps (jvz). 35
org.apache.maven.repository.legacy.resolver.transform.AbstractVersionTransformation Line
try and refactor to remove abstract methods - not particular happy about current design 45


Number of occurrences found in the code: 44

org.apache.maven.artifact.manager.DefaultWagonManager Line
this should be illegal in settings.xml 169
org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager Line
should this be inside the above check? touch file so that this is not checked again until interval has passed 159
currently this is first wins, but really we should take the latest by comparing either the snapshot timestamp, or some other timestamp later encoded into the metadata. 190
this needs to be repeated here so the merging doesn't interfere with the written metadata - we'd be much better having a pristine input, and an ongoing metadata for merging instead 192
this could be a lot nicer... should really be in the snapshot transformation? 221
org.apache.maven.artifact.resolver.DebugResolutionListener Line
better way than static? this might hide messages in a reactor 88
org.apache.maven.artifact.resolver.DefaultArtifactResolver Line
hack because metadata isn't generated in m2e correctly and i want to run the maven i have in the workspace 374
org.apache.maven.project.MavenProjectBuilder Line
maven-site-plugin -- Vincent, Dennis and Lukas are checking but this doesn't appear to be required anymore. 42
remote-resources-plugin 46
remote-resources-plugin 51
this is only to provide a project for plugins that don't need a project to execute but need some of the values from a MavenProject. Ideally this should be something internal and nothing outside Maven would ever need this so it should not be exposed in a public API 56
org.apache.maven.project.inheritance.DefaultModelInheritanceAssembler Line
Remove this! 55
Remove this! 307
Remove this! 535
This should eventually be migrated to DefaultPathTranslator. 665
Move this to plexus-utils' PathTool. 701
org.apache.maven.repository.legacy.DefaultUpdateCheckManager Line
throw something instead? 93
throw something instead? 143
org.apache.maven.repository.legacy.DefaultWagonManager Line
remove the update check manager 59
separate into retriever and publisher 60
remove hardcoding of checksum logic 61
configure on repository 351
configure these on the repository 561
shouldn't need a file intermediatary - improve wagon to take a stream 595
org.apache.maven.repository.legacy.repository.DefaultArtifactRepositoryFactory Line
use settings? 40
org.apache.maven.repository.legacy.resolver.DefaultArtifactCollectorTest Line
use newest conflict resolver 169
use newest conflict resolver 188
org.apache.maven.repository.legacy.resolver.DefaultLegacyArtifactCollector Line
we probably want to warn the user that he is building an artifact with different values than in dependencyManagement 226
Does this check need to happen here? Had to add the same call below when we iterate on child nodes -- will that suffice? 249
shouldn't need to double up on this work, only done for simplicity of handling recommended version but the restriction is identical 272
ick. this forces the OCE that should have come from the previous call. It is still correct 276
add better exception that can detail the two conflicting artifacts 354
add better exception 364
should this be part of mediation? previous one is more dominant 370
maybe its better to just pass the range through to retrieval and use a transformation? 489
might be better to have source.retrieve() throw a specific exception for this situation and catch here rather than have it return null 552
org.apache.maven.repository.legacy.resolver.conflict.NewestConflictResolver Line
log message or throw exception? 57
org.apache.maven.repository.legacy.resolver.conflict.OldestConflictResolver Line
log message or throw exception? 57
org.apache.maven.repository.legacy.resolver.transform.AbstractVersionTransformation Line
also do this logging for other metadata? 108
figure out way to avoid duplicated message 109
org.apache.maven.repository.metadata.MetadataResolutionException Line
Auto-generated constructor stub 28
Auto-generated constructor stub 34
Auto-generated constructor stub 40
Auto-generated constructor stub 46