You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Christian Schulte (JIRA)" <ji...@apache.org> on 2017/03/25 22:38:41 UTC

[jira] [Commented] (MNG-2893) Update the DefaultPluginManager to not use a project depMan for controlling it's transitive dependencies

    [ https://issues.apache.org/jira/browse/MNG-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15942012#comment-15942012 ] 

Christian Schulte commented on MNG-2893:
----------------------------------------

Issue is fixed in the master branch of [my private maven repository on github|https://github.com/ChristianSchulte/maven/tree/master]. When interested, you can cherry pick the commit to your own repository and create a pull request for the apache master branch with just this commit yourself from there.


> Update the DefaultPluginManager to not use a project depMan for controlling it's transitive dependencies
> --------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-2893
>                 URL: https://issues.apache.org/jira/browse/MNG-2893
>             Project: Maven
>          Issue Type: Task
>          Components: Plugins and Lifecycle
>    Affects Versions: 2.0.5
>            Reporter: Jason van Zyl
>             Fix For: 3.2.x, 3.5.1-candidate
>
>
> An adjustment to MNG-1577. The classpath for plugins should not be affected by a projects depMan.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)