[MNG-1895] Dependencies in two paths are not added to resolution when scope needs to be updated in the nearest due to any of nearest parents

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.0.1, 2.0.2
• Fix Version/s: 2.0.3
• Component/s: Artifacts and Repositories
• Assignee: Carlos Sanchez Gonzalez
• Reporter: Carlos Sanchez Gonzalez
• Created: 24/Dec/05 18:12
• Updated: 21/Nov/10 10:12
• Resolved: 24/Jan/06 17:28

Description

scopes are not correctly calculated for this case

my pom: a compile, b test
a: c compile, d compile
b: d compile

then d ends in test scope because d is closer to my project through the path b-d

I think scope importance should also be taken into account

Issue Links

• is duplicated by: MNG-1568 test-jar dependency clobbers transitive dependency
• is duplicated by: MNG-1571 Wrong calculation of transient dependecies if artifact is referenced from different scopes
• relates to: MNG-2686 POM dependency scope auto-downgrades from provided to test
• relates to: MNG-4675 Compile scoped dependencies replaced by test
• relates to: MNG-4789 [regression] Difference in compile scope dependency resolution
• relates to: MNG-4724 Plugin runtime classpath during execution differs from runtime classpath during building when conflicts with test/provided scope dependencies are involved