[
https://jira.codehaus.org/browse/MNG-5564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MNG-5564.
-------------------------------
Resolution: Not A Bug
Assignee: Robert Scholte
So here's what's happening: since you only specified prefix (in this case:
source) for the plugin, Maven has to search for the fully qualified name. First
it'll go through all the build-plugins, followed by the
pluginManagement-plugins. For every plugin Maven needs to download the jar to
discover its
[prefix|http://maven.apache.org/plugin-tools/maven-plugin-plugin/examples/generate-descriptor.htm],
which is configured when building/generating the plugin.
So you can't prevent Maven to download unless you use the fully qualified name.
If you would have defined the maven-source-plugin before the lifecycle-mapping,
you wouldn't have seen this message.
> Direct mojo invocation attempts to download unrelated plugins from
> pluginManagement
> -----------------------------------------------------------------------------------
>
> Key: MNG-5564
> URL: https://jira.codehaus.org/browse/MNG-5564
> Project: Maven
> Issue Type: Bug
> Affects Versions: 2.2.1, 3.1.1, 3.2.5
> Reporter: Konrad Windszus
> Assignee: Robert Scholte
> Priority: Critical
> Attachments: pom.xml
>
>
> Attached is an example pom. Whenever you run mvn source:jar on it, it tries
> to download org.eclipse.m2e:lifecycle-mapping:1.0.0 although it is only
> listed in the pluginManagement. If using a regular goal, that dependency is
> never downloaded.
> That dependency does not exist, as it is only a way to configure m2e, so
> there is nowhere such an artifact (mentioned by Igor Fedorenko in
> http://permalink.gmane.org/gmane.comp.ide.eclipse.plugins.m2eclipse.user/6218).
> Why is the maven source plugin trying to download that artifact?
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
