[MRESOLVER-9] DefaultDependencyCollector does not correctly handle dependency management

• 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: 11/Dec/16 00:18
• Updated: 20/Jan/22 12:21

Description

During dependency processing the DependencySelector is called to decide if a dependency is to be selected. The call to DependencySelector.selectDependency() is performed with the unmanaged dependency, but needs to be performed with the managed dependency. With the fix applied, the result no longer contains dependencies whose scope or optionality has been managed to not be part of the result (correct behaviour). Without the fix applied, the result contains dependencies with a managed scope or optionality not filtered out by the DependencySelector in use (incorrect behaviour).

Issue Links

• blocks: MNG-6135 Maven plugins and core extensions are not dependencies, they should be resolved the same way as projects.
• blocks: MNG-5935 Optional true getting lost in managed dependencies when transitive
• blocks: MNG-7003 Inconsistent dependency tree
• blocks: MNG-5227 The 'optional' flag of a dependency should be manageable.
• is depended upon by: MRESOLVER-12 Addition of unit tests for DependencySelector implementations
• is related to: MRESOLVER-235 Managed dependencies are not honoured when resolving a dependency graph
• is required by: MNG-6139 Addition of command line option 'legacy-dependency-management'.
• links to: GitHub Pull Request #145
• links to: Original bug report.