[jira] [Reopened] (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 ] Christian Schulte reopened MNG-6135: > 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.3.15#6346)
[jira] [Reopened] (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 reopened MNG-6135: --- Maven 3.4.0 has been dropped. See [this thread|https://mail-archives.apache.org/mod_mbox/maven-dev/201701.mbox/%3CCA%2BnPnMx-e7kGYy3Hp87v8hLGdhp1q%3DtKLx_6QuZ4kGUqHEBGcw%40mail.gmail.com%3E] for more details. This issue will need to be re-scheduled for a Maven release in the (hopefully near) future. > 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)
[jira] [Reopened] (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 ] Christian Schulte reopened MNG-6135: Re-opening to edit links. > 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 > > > can you explain the logic, please? > I don't understand why "they should be resolved the same way as project", > what it really means and what impact it has: I just see that everything is > currently failing: it's a mess!!! -- This message was sent by Atlassian JIRA (v6.3.4#6332)