maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MNG-6135) Maven plugins and core extensions are not dependencies, they should be resolved the same way as projects.
Date Mon, 11 Dec 2017 16:35:24 GMT

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

Hudson commented on MNG-6135:
-----------------------------

Build unstable in Jenkins: Maven TLP (wip) » maven » pre-reset-master #3

See https://builds.apache.org/job/maven-wip/job/maven/job/pre-reset-master/3/

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

Mime
View raw message