[
https://issues.apache.org/jira/browse/MNG-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15789897#comment-15789897
]
Hudson commented on MNG-6135:
-----------------------------
SUCCESS: Integrated in Jenkins build maven-3.x #1478 (See
[https://builds.apache.org/job/maven-3.x/1478/])
[MNG-6135] Maven plugins and core extensions are not dependencies, they
(schulte:
[http://git-wip-us.apache.org/repos/asf/?p=maven.git&a=commit&h=6d68777c7ed6de2ad8fca6495b65b138bc1f7085])
* (edit)
maven-core/src/main/java/org/apache/maven/plugin/internal/DefaultPluginDependenciesResolver.java
> 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
> Assignee: Christian Schulte
> Priority: Critical
> Fix For: 3.4.0
>
>
> 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.4#6332)
