Brian Fox:
I put this on my desktop and ran:
c:\Users\brianf\Desktop>mvn help:effective-pom
And it started downloading all updated versions of the
plugins...plugins that aren't being used in this execution and aren't
referenced in the pom directly.
In short, the plugin JARs (and only those) are downloaded to resolve the
plugin prefix "help" from your command. Executing
mvn org.apache.maven.plugins:maven-help-plugin:effective-pom
wouldn't have downloaded anything but the Help Plugin and its dependencies.
As a reminder, to resolve a plugin prefix Maven looks in these locations
1. project.build.plugins
2. project.build.pluginManagement.plugins
3. settings.pluginGroups
See also [0].
The other thing that contributes to your log is the fact that Maven 3
merges the lifecycle bindings into the effective POM (see also [1]). In
other words, the Compiler Plugin, Resources Plugin etc. will now show up
in the effective POM's build/plugins section (along with their default
executions) as if the user had defined them.
So to summarize, the maven-x-plugin.jar was downloaded because
a) maven-x-plugin was present in project.build.plugins
b) project.build.plugins was searched for a prefix match with "help"
Benjamin
[0] http://jira.codehaus.org/browse/MNG-2432
[1] http://jira.codehaus.org/browse/MPH-13
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
