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: 7

share with DefaultPluginMappingManager. 297
split instantiation (versioning, plugin mappings) from definition29
Consolidate this logic with the PluginParameterExpressionEvaluator, minus deprecations/bans.60
Remove the throws clause.104
Consolidate this logic with the PluginParameterExpressionEvaluator, minus deprecations/bans.33
you don't need the container in here with the active maps (jvz).35
try and refactor to remove abstract methods - not particular happy about current design45


Number of occurrences found in the code: 44

this should be illegal in settings.xml169
should this be inside the above check? touch file so that this is not checked again until interval has passed159
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.188
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 instead190
this could be a lot nicer... should really be in the snapshot transformation?217
better way than static? this might hide messages in a reactor88
hack because metadata isn't generated in m2e correctly and i want to run the maven i have in the workspace345
maven-site-plugin -- Vincent, Dennis and Lukas are checking but this doesn't appear to be required anymore.39
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 API53
Remove this!55
Remove this!307
Remove this!538
This should eventually be migrated to DefaultPathTranslator.668
Move this to plexus-utils' PathTool.704
throw something instead?93
throw something instead?143
remove the update check manager54
separate into retriever and publisher55
remove hardcoding of checksum logic56
configure on repository319
configure these on the repository529
shouldn't need a file intermediatary - improve wagon to take a stream563
use settings?40
use newest conflict resolver169
use newest conflict resolver188
we probably want to warn the user that he is building an artifact with different values than in dependencyManagement226
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 identical272
ick. this forces the OCE that should have come from the previous call. It is still correct276
add better exception that can detail the two conflicting artifacts354
add better exception364
should this be part of mediation? previous one is more dominant370
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 null552
log message or throw exception?57
log message or throw exception?57
also do this logging for other metadata?108
figure out way to avoid duplicated message109
Auto-generated constructor stub28
Auto-generated constructor stub34
Auto-generated constructor stub40
Auto-generated constructor stub46