Dependency configuration in DependencyManagement with exclusions is ignored
---------------------------------------------------------------------------
Key: MECLIPSE-368
URL: http://jira.codehaus.org/browse/MECLIPSE-368
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Affects Versions: 2.4
Environment: Ubuntu Linux 7.10
Reporter: jh
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
