[
https://jira.codehaus.org/browse/MSOURCES-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=334521#comment-334521
]
Konrad Windszus commented on MSOURCES-67:
-----------------------------------------
Compare with https://bugs.eclipse.org/bugs/show_bug.cgi?id=367870. This rather
seems to be a bug in Maven core as it happens whenever a Mojo goal is directly
invoked. Please decide whether this is the desired behaviour. If that is the
case, I would request a dummy artifact for
org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 being uploaded to Maven Central as
this is currently the recommended way to influence the m2e lifecycle mapping
(http://wiki.eclipse.org/M2E_plugin_execution_not_covered#ignore_plugin_goal).
> Maven source plugin leads to plugins being downloaded only listed in
> pluginManagement
> -------------------------------------------------------------------------------------
>
> Key: MSOURCES-67
> URL: https://jira.codehaus.org/browse/MSOURCES-67
> Project: Maven Source Plugin
> Issue Type: Bug
> Affects Versions: 2.2.1
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
