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

Posted to issues@maven.apache.org by "Stephen Connolly (JIRA)" <ji...@apache.org> on 2018/06/17 21:38:02 UTC

[jira] [Updated] (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:all-tabpanel ]

Stephen Connolly updated MNG-2893:
----------------------------------
    Fix Version/s:     (was: 3.5.x-candidate)
                   3.6.x-candidate

> 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
>            Priority: Major
>             Fix For: 3.2.x, 3.6.x-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
(v7.6.3#76005)