[MNG-6135] Maven plugins and core extensions are not dependencies, they should be resolved the same way as projects.

[jira-importer]

Christian Schulte opened MNG-6135 and commented

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)

---

Issue Links:

• MRESOLVER-8 ScopeDependencySelector incorrectly de-selects direct dependencies
  ("is blocked by")

• MRESOLVER-9 DefaultDependencyCollector does not correctly handle dependency management
  ("is blocked by")

• MRESOLVER-10 New 'TransitiveDependencyManager' supporting transitive dependency management
  ("is blocked by")

• MNG-8559 Rewrite DefaultPluginManager with Maven 4 API
  ("Is contained by")

• MNG-5739 Adding a test dependency can move dependencies from the compile scope to the test scope

• MPLUGIN-321 improve documentation on maven-plugin-annotations telling that optional=true is sufficient

• MEAR-246 Upgrade the EAR lifecycle to use the maven-resources-plugin 3.0.2.
  ("breaks")

• MPLUGIN-296 java.lang.ClassNotFoundException: org.apache.maven.plugins.annotations.Execute
  ("breaks")

• MWAR-400 Upgrade the WAR lifecycle to use the maven-resources-plugin 3.0.2
  ("breaks")

• MRESOURCES-234 Upgrade of commons-io to 2.5 and correction of invalid scope.
  ("breaks")

• MPMD-230 Required class missing: org/apache/commons/io/IOUtils
  ("breaks")

Remote Links:

• Page
  

1 votes, 9 watchers

[jira-importer]

Christian Schulte commented

Re-opening to edit links.

[jira-importer]

Stephen Connolly commented

Maven 3.4.0 has been dropped. See this thread for more details.

This issue will need to be re-scheduled for a Maven release in the (hopefully near) future.

[jira-importer]

Michael Osipov commented

Why is this fixed, where is the commit link?

[jira-importer]

Christian Schulte commented

See this thread on dev@. Issue is resolved, not closed.

[jira-importer]

Christian Schulte commented

Issue is fixed in the master branch of my private maven repository on github. 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.

[jira-importer]

mike duigou commented

Why was this never cherry picked back in to maven master from the abandoned 3.4.0 branch?

[jira-importer]

Michael Osipov commented

mike duigou, because this is a lot of work? Do you want to give it a try?