[MNG-3090] Nearest dependency, which is not included by a filter, wins, although a farthest dependency, which is included by the same filter, does not win.

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 2.0.7
• Component/s: Artifacts and Repositories
• Flags: Patch
• Assignee: Jason van Zyl
• Reporter: Christian Schulte
• Created: 05/Jul/07 19:24
• Updated: 08/Feb/20 15:41
• Resolved: 19/Jan/14 14:13

Description

There seems to be a problem with transitive dependencies and the nearest wins strategy. The nearest dependency wins, although a filter is in use which will not include that dependency when there is the same dependency at a deeper level, where it is included by the same filter. The nearest dependency gets discarded (e.g. is missing on the compile classpath) although the farthest dependency would have been included. Please see the comments in the attached patch.

Issue Links

• is related to: MNG-3089 DefaultArtifactCollector does not filter ResolutionListener events