[jira] [Commented] (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:comment-tabpanel=17215686#comment-17215686
]
Michael Osipov commented on MNG-6135:
-
[~bondolo], because this is a lot of work? Do you want to give it a try?
> 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.7.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
(v8.3.4#803005)
[jira] [Commented] (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:comment-tabpanel=17212742#comment-17212742
]
mike duigou commented on MNG-6135:
--
Why was this never cherry picked back in to maven master from the abandoned
3.4.0 branch?
> 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.7.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
(v8.3.4#803005)
[jira] [Commented] (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:comment-tabpanel=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)
[jira] [Commented] (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:comment-tabpanel=15942030#comment-15942030
]
Christian Schulte commented on MNG-6135:
Issue is fixed in the master branch of [my private maven repository on
github|https://github.com/ChristianSchulte/maven/tree/master]. When interested,
you can cherry pick the commit to your own repository and create a pull request
for the apache master branch with just this commit yourself from there.
> 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] [Commented] (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:comment-tabpanel=15849302#comment-15849302
]
Christian Schulte commented on MNG-6135:
See [this
thread|http://www.mail-archive.com/dev@maven.apache.org/msg112480.html] on
dev@. Issue is resolved, not closed.
> 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.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] [Commented] (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:comment-tabpanel=15848675#comment-15848675
]
Michael Osipov commented on MNG-6135:
-
Why is this fixed, where is the commit link?
> 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.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] [Commented] (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:comment-tabpanel=15790023#comment-15790023
]
Hudson commented on MNG-6135:
-
SUCCESS: Integrated in Jenkins build maven-3.x #1479 (See
[https://builds.apache.org/job/maven-3.x/1479/])
[MNG-6135] Maven plugins and core extensions are not dependencies, they
(schulte:
[http://git-wip-us.apache.org/repos/asf/?p=maven.git=commit=859651acfc73af2a2afcd044306eaa0e5e5ac51a])
* (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)
[jira] [Commented] (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:comment-tabpanel=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=commit=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)
[jira] [Commented] (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:comment-tabpanel=15766068#comment-15766068
]
Hudson commented on MNG-6135:
-
SUCCESS: Integrated in Jenkins build maven-3.x #1466 (See
[https://builds.apache.org/job/maven-3.x/1466/])
[MNG-6135] Maven plugins and core extensions are not dependencies, they
(schulte: rev e8a0af6e649b21a8fd5f7d59ef8b559ed39fcf16)
* (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.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (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:comment-tabpanel=15758255#comment-15758255 ] Hudson commented on MNG-6135: - SUCCESS: Integrated in Jenkins build maven-3.x Jigsaw #49 (See [https://builds.apache.org/job/maven-3.x%20Jigsaw/49/]) [MNG-6135] Maven plugins and core extensions are not dependencies, they (schulte: rev 06580630a3b09143770fd8eeda6c86f70a016f4d) * (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 > > > 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)
[jira] [Commented] (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:comment-tabpanel=15758251#comment-15758251 ] Hudson commented on MNG-6135: - SUCCESS: Integrated in Jenkins build maven-3.x #1459 (See [https://builds.apache.org/job/maven-3.x/1459/]) [MNG-6135] Maven plugins and core extensions are not dependencies, they (schulte: rev 06580630a3b09143770fd8eeda6c86f70a016f4d) * (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 > > > 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)
[jira] [Commented] (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:comment-tabpanel=15758163#comment-15758163 ] Hudson commented on MNG-6135: - SUCCESS: Integrated in Jenkins build maven-3.x Jigsaw #48 (See [https://builds.apache.org/job/maven-3.x%20Jigsaw/48/]) [MNG-6135] Maven plugins and core extensions are not dependencies, they (schulte: rev bbffde98fdf3c46d7698c300ca074ed980fa921e) * (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 > > > 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)
[jira] [Commented] (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:comment-tabpanel=15758160#comment-15758160 ] Hudson commented on MNG-6135: - SUCCESS: Integrated in Jenkins build maven-3.x #1457 (See [https://builds.apache.org/job/maven-3.x/1457/]) [MNG-6135] Maven plugins and core extensions are not dependencies, they (schulte: rev bbffde98fdf3c46d7698c300ca074ed980fa921e) * (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 > > > 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)
[jira] [Commented] (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:comment-tabpanel=15758103#comment-15758103 ] Hudson commented on MNG-6135: - SUCCESS: Integrated in Jenkins build maven-3.x #1456 (See [https://builds.apache.org/job/maven-3.x/1456/]) [MNG-6135] Maven plugins and core extensions are not dependencies, they (schulte: rev 80f2fd6375ad5311031929c1bbaf87aa42a3c53a) * (edit) maven-core/src/main/java/org/apache/maven/plugin/internal/PlexusUtilsInjector.java * (edit) maven-core/src/main/java/org/apache/maven/plugin/internal/WagonExcluder.java [MNG-6135] Maven plugins and core extensions are not dependencies, they (schulte: rev 286c7ffba1696053274c5da6cad4336f678fceee) * (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 > > > 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)
[jira] [Commented] (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:comment-tabpanel=15758099#comment-15758099 ] Hudson commented on MNG-6135: - SUCCESS: Integrated in Jenkins build maven-3.x Jigsaw #47 (See [https://builds.apache.org/job/maven-3.x%20Jigsaw/47/]) [MNG-6135] Maven plugins and core extensions are not dependencies, they (schulte: rev 80f2fd6375ad5311031929c1bbaf87aa42a3c53a) * (edit) maven-core/src/main/java/org/apache/maven/plugin/internal/WagonExcluder.java * (edit) maven-core/src/main/java/org/apache/maven/plugin/internal/PlexusUtilsInjector.java [MNG-6135] Maven plugins and core extensions are not dependencies, they (schulte: rev 286c7ffba1696053274c5da6cad4336f678fceee) * (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 > > > 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)
[jira] [Commented] (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:comment-tabpanel=15756472#comment-15756472 ] Hudson commented on MNG-6135: - SUCCESS: Integrated in Jenkins build maven-3.x Jigsaw #45 (See [https://builds.apache.org/job/maven-3.x%20Jigsaw/45/]) [MNG-6135] Maven plugins and core extensions are not dependencies, they (schulte: rev 14bff2c5c5a0729e39f7d0fc62ed733222c90a18) * (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 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (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:comment-tabpanel=15756466#comment-15756466 ] Hudson commented on MNG-6135: - SUCCESS: Integrated in Jenkins build maven-3.x #1453 (See [https://builds.apache.org/job/maven-3.x/1453/]) [MNG-6135] Maven plugins and core extensions are not dependencies, they (schulte: rev 14bff2c5c5a0729e39f7d0fc62ed733222c90a18) * (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 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (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:comment-tabpanel=15756281#comment-15756281 ] Hudson commented on MNG-6135: - SUCCESS: Integrated in Jenkins build maven-3.x Jigsaw #44 (See [https://builds.apache.org/job/maven-3.x%20Jigsaw/44/]) [MNG-6135] Maven plugins and core extensions are not dependencies, they (schulte: rev 9fef375bb0947bdc8ae5ca1ffe5b69d3fd31a4ab) * (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 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (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:comment-tabpanel=15756277#comment-15756277 ] Hudson commented on MNG-6135: - SUCCESS: Integrated in Jenkins build maven-3.x #1452 (See [https://builds.apache.org/job/maven-3.x/1452/]) [MNG-6135] Maven plugins and core extensions are not dependencies, they (schulte: rev 9fef375bb0947bdc8ae5ca1ffe5b69d3fd31a4ab) * (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 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (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:comment-tabpanel=15756217#comment-15756217 ] Hudson commented on MNG-6135: - SUCCESS: Integrated in Jenkins build maven-3.x #1451 (See [https://builds.apache.org/job/maven-3.x/1451/]) [MNG-6135] Maven plugins and core extensions are not dependencies, they (schulte: rev 15a947faeca03c74505605c290e821b0d7a59dc3) * (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 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
