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

ASF GitHub Bot commented on MNG-2893:
-------------------------------------

GitHub user ChristianSchulte opened a pull request:

    https://github.com/apache/maven/pull/144

    [MNG-2893] Update the DefaultPluginManager to not use a project depMa…

    …n for controlling it's transitive dependencies

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ChristianSchulte/maven MNG-2893

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/maven/pull/144.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #144
    
----
commit 1de1ce1fdc50a8574a6b0e32ce4adc8389fcf73a
Author: Christian Schulte <cs@...>
Date:   2017-03-25T22:01:03Z

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

----


> 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.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
(v6.4.14#64029)

Reply via email to