[MRESOLVER-8] ScopeDependencySelector incorrectly de-selects direct dependencies

• Type: Bug
• Status: Reopened
• Priority: Critical
• Resolution: Unresolved
• Fix Version/s: Maven Artifact Resolver 1.2.0 pre-reset
• Component/s: Resolver
• Assignee: Unassigned
• Reporter: Christian Schulte
• Created: 14/Nov/16 00:22
• Updated: 21/Nov/20 18:36

Description

The ScopeDependencySelector decides if a node is a direct dependency or transitive dependency differently based on the request performed. For the CollectRequest.setRootArtifact(Artifact) case, the class is working correctly. For the CollectRequest.setRoot(Dependency) case, the class is de-selecting direct dependencies instead of transitive dependencies.

Issue Links

• blocks: MNG-6135 Maven plugins and core extensions are not dependencies, they should be resolved the same way as projects.
• 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 depended upon by: MRESOLVER-12 Addition of unit tests for DependencySelector implementations
• is related to: MPLUGIN-321 improve documentation on maven-plugin-annotations telling that optional=true is sufficient
• links to: GitHub Pull Request #107