You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Stephen Connolly (JIRA)" <ji...@apache.org> on 2018/06/17 21:43:02 UTC
[jira] [Updated] (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:all-tabpanel ]
Stephen Connolly updated MNG-6135:
----------------------------------
Fix Version/s: (was: 3.6.0-candidate)
3.6.x-candidate
> 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.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
(v7.6.3#76005)