[jira] [Commented] (MNG-6135) Maven plugins and core extensions are not dependencies, they should be resolved the same way as projects.

["Christian Schulte (JIRA)" <ji...@apache.org>]

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

Christian Schulte commented on MNG-6135:
----------------------------------------

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.


> Maven plugins and core extensions are not dependencies, they should be resolved the same way as projects.
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-6135
>                 URL: https://issues.apache.org/jira/browse/MNG-6135
>             Project: Maven
>          Issue Type: Bug
>            Reporter: Christian Schulte
>            Priority: Critical
>             Fix For: 3.6.0-candidate
>
>
> Due to a bug in the Maven resolver, plugin and core extensions were resolved incorrectly: the direct {{test}} and {{provided}} dependencies were ignored.
> Ironically, this fix breaks some plugins because direct {{test}} dependencies now take precedence over transitive {{compile}} one: see MNG-5739
> (we know only one case where {{provided}} case has an impact: MPLUGIN-296, and in this only case, the new behaviour is more consistent than the previous)
>   



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