[
http://jira.codehaus.org/browse/MECLIPSE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98868
]
Klaus Brunner commented on MECLIPSE-262:
----------------------------------------
I'm apparently having the same problem. I wrote this up for opening a new bug
report, but I'll attach it anyway in case it helps:
Find attached a sample WAR project (testcase.zip) that lists
commons-configuration and commons-jxpath as dependencies. Both of these
artifacts depend (directly or transitively) on commons-collections, although
there is a version conflict: c-configuration requires c-collections 3.2, but
c-jxpath requires c-collections 2.0.
Running "mvn clean eclipse:eclipse package" has the following effect:
1) The Eclipse classpath includes commons-collections-3.2.jar
2) The Maven-built WAR archive in the target folder includes
commons-collections-2.0.jar (WEB-INF/lib).
Also seen on attached screenshot.
In this specific case, the result is that everything works fine in Eclipse, but
when the Maven-built WAR is deployed, it fails because c-collections 3.2 is
definitely required at runtime. Not good.
> 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: dependency resolution
> Affects Versions: 2.3
> Environment: Maven 2.0.6, 2.0.4
> Reporter: Carlos Sanchez
> Attachments: compile.txt, eclipse.txt, 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
