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

• Type: Bug
• Status: Reopened
• Priority: Critical
• Resolution: Unresolved
• Fix Version/s: 4.0.x-candidate
• Assignee: Unassigned
• Reporter: Christian Schulte
• Created: 15/Dec/16 22:27
• Updated: 27/Nov/20 15:38

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)

Issue Links

• breaks: 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
• is blocked by: 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 related to: MPLUGIN-321 improve documentation on maven-plugin-annotations telling that optional=true is sufficient
• relates to: MNG-5739 Adding a test dependency can move dependencies from the compile scope to the test scope
• mentioned in: Page Loading...