[MNG-4790] Dependency resolution issue with provided scope

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 3.0-beta-3
• Component/s: Dependencies
• Assignee: Benjamin Bentmann
• Reporter: Paul Gier
• Created: 02/Sep/10 13:57
• Updated: 08/Sep/10 04:40
• Resolved: 07/Sep/10 13:19

Description

There is a slight difference in the dependency resolution between maven-3-beta-2 and maven-3-beta-3. It seems to be related to the "provided" scope, but I'm having some difficulty narrowing down the problem. I've attached a POM which demonstrates the problem. Using maven-3-beta-2 the ejb3-persistence jar is included in the compile classpath. Using maven-3-beta-3, this jar is not included in the compile classpath.

Issue Links

• is related to: MNG-820 Over-zealous transitive dependencies during mediation
• is related to: MNG-4761 Plugin-level dependency scope causes some plugin classpaths to be incorrect
• relates to: MNG-4800 Conflict resolution does not pick sub tree of nearest dependency if farther conflicting dependency has wider scope