[
http://jira.codehaus.org/browse/MECLIPSE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=176873#action_176873
]
benson margulies commented on MECLIPSE-262:
-------------------------------------------
I'm seeing a variation on this.
Parent POM has dependencyManagement with log4j and a list of exclusions.
Users of the parent POM end up with classpath entries for the excluded
dependencies.
dependency:tree correctly shows no sign of the excluded dependencies.
> Maven compilation and eclipse classpath don't match with conflicting versions
> at same dependency depth
> ------------------------------------------------------------------------------------------------------
>
> Key: MECLIPSE-262
> URL: http://jira.codehaus.org/browse/MECLIPSE-262
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : Dependencies resolution and build path
> (.classpath)
> Affects Versions: 2.3
> Environment: Maven 2.0.6, 2.0.4
> Reporter: Carlos Sanchez
> Attachments: compile.txt, eclipse.txt, screenshot-1.jpg, testcase.zip
>
>
> https://svn.apache.org/repos/asf/maven/components/trunk/maven-core rev# 533182
> compile uses plexus-component-api-1.0-alpha-24 (the right one)
> eclipse:eclipse uses plexus-component-api-1.0-alpha-16
--
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
