[
https://issues.apache.org/jira/browse/MNG-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MNG-6135:
-------------------------------
Description:
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)
was:
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
> 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)
