[MECLIPSE-368] Dependency configuration in DependencyManagement with exclusions is ignored

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.4
• Component/s: Core : Dependencies resolution and build path (.classpath)
• Environment: Ubuntu Linux 7.10
• Assignee: Arnaud Heritier
• Reporter: Jannik Hansen
• Created: 16/Jan/08 03:50
• Updated: 08/Sep/16 23:16
• Resolved: 26/Sep/09 18:36

Description

A transitive dependency which is defined in the DependencyManagement section with exclusions does not take these exclusions into account when generating an eclipse classpath.

Example:

• childProject has a dependency 'acegi-security-tiger'
• parentProject has a dependencyManagement section that defines the version and the exclusions
• acegi-security-tiger has a transitive dependency to acegi-security
• parentProject has defined acegi-security and a number of exclusions one of which is spring-remoting 1.2.7
• childProject's classpath ends up with spring-remoting 1.2.7 as dependency
• we are using spring 2.5.1 which does not have spring-remoting

If I check dependencies with dependency:tree -Dscope=null the dependency resolving of acegi-security-tiger stops with acegi-security and no other transitive dependencies are added (all are excluded)

Workaround is to add acegi-security in childProject's pom.

Main concern here is that dependency resolution in the eclipse plugin seems to be different from the dependency plugin.

Issue Links

• duplicates: MECLIPSE-603 Exclusions are not applied on transitive dependencies