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

Posted to issues@maven.apache.org by "mike duigou (Jira)" <ji...@apache.org> on 2020/10/13 00:14:00 UTC

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

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

mike duigou commented on MNG-6135:
----------------------------------

Why was this never cherry picked back in to maven master from the abandoned 3.4.0 branch?

> 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.7.x-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
(v8.3.4#803005)