maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <j...@codehaus.org>
Subject [jira] (MNG-5564) Direct mojo invocation attempts to download unrelated plugins from pluginManagement
Date Fri, 13 Feb 2015 16:55:19 GMT

    [ https://jira.codehaus.org/browse/MNG-5564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=363269#comment-363269
] 

Robert Scholte commented on MNG-5564:
-------------------------------------

What might be interesting: this only happens when using the shortened plugin name. If you
use the fully qualified name (i.e {{org.apache.maven.plugins:maven-source-plugin:jar}} ) you
don't get the warning. It's like when Maven tries to find the matching plugin based on just
"source", it'll do a bit too much when looping over the available plugins in the pom.xml.
Still happened with 3.2.5.

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

Mime
View raw message