You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Carlos Sanchez (JIRA)" <ji...@codehaus.org> on 2007/04/27 23:01:26 UTC
[jira] Created: (MECLIPSE-262) Maven compilation and eclipse
classpath don't match
Maven compilation and eclipse classpath don't match
---------------------------------------------------
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
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
[jira] Commented: (MECLIPSE-262) Maven compilation and eclipse
classpath don't match with conflicting versions at same dependency depth
Posted by "Jorg Heymans (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94702 ]
Jorg Heymans commented on MECLIPSE-262:
---------------------------------------
I think we're suffering from the same problem. In our root pom <depMgmt> we declared
<dependency>
<groupId>commons-logging</groupId>
<artifactId>commons-logging</artifactId>
<version>1.1</version>
<exclusions>
<exclusion>
<artifactId>logkit</artifactId>
<groupId>logkit</groupId>
</exclusion>
<exclusion>
<artifactId>avalon-framework</artifactId>
<groupId>avalon-framework</groupId>
</exclusion>
<exclusion>
<groupId>javax.servlet</groupId>
<artifactId>servlet-api</artifactId>
</exclusion>
</exclusions>
</dependency>
(note the exclusion of avalon-framework)
However, the eclipse plugin still selects avalon-framework :
[INFO] [eclipse:eclipse]
[DEBUG] org.apache.cocoon:cocoon-sitemap-impl:jar:1.0.0-RC1-SNAPSHOT (selected for null)
[DEBUG] commons-collections:commons-collections:jar:3.2:compile (selected for compile)
[DEBUG] commons-jxpath:commons-jxpath:jar:1.2:compile (selected for compile)
[DEBUG] junit:junit:jar:3.8:compile (applying version: 3.8.2)
[DEBUG] junit:junit:jar:3.8.2:compile (applying scope: test)
[DEBUG] junit:junit:jar:3.8.2:test (selected for test)
[DEBUG] xml-apis:xml-apis:jar:2.0.2:compile (applying version: 1.3.02)
[DEBUG] xml-apis:xml-apis:jar:1.3.02:compile (selected for compile)
[DEBUG] commons-logging:commons-logging:jar:1.0:compile (applying version: 1.1)
[DEBUG] commons-logging:commons-logging:jar:1.1:compile (selected for compile)
[DEBUG] log4j:log4j:jar:1.2.12:compile (applying version: 1.2.14)
[DEBUG] log4j:log4j:jar:1.2.14:compile (selected for compile)
[DEBUG] logkit:logkit:jar:1.0.1:compile (selected for compile)
[DEBUG] avalon-framework:avalon-framework:jar:4.1.3:compile (selected for compile)
[DEBUG] javax.servlet:servlet-api:jar:2.3:compile (applying version: 2.4)
[DEBUG] javax.servlet:servlet-api:jar:2.4:compile (selected for compile)
[DEBUG] commons-collections:commons-collections:jar:2.0:compile (applying version: 3.2)
[DEBUG] javax.servlet:servlet-api:jar:2.4:provided (not setting scope to: compile; local scope provided wins)
The dependency plugin shows correct dependency resolution (no avalon-framework)
[INFO] [dependency:resolve]
[INFO]
[INFO] The following files have been resolved:
[INFO] aopalliance:aopalliance:jar:1.0 (scope = compile)
[INFO] commons-collections:commons-collections:jar:3.2 (scope = compile)
[INFO] commons-io:commons-io:jar:1.3.1 (scope = compile)
[INFO] commons-jxpath:commons-jxpath:jar:1.2 (scope = compile)
[INFO] commons-lang:commons-lang:jar:2.3 (scope = compile)
[INFO] commons-logging:commons-logging:jar:1.1 (scope = compile)
[INFO] concurrent:concurrent:jar:1.3.4 (scope = compile)
[INFO] jakarta-regexp:jakarta-regexp:jar:1.4 (scope = compile)
[INFO] javax.servlet:servlet-api:jar:2.4 (scope = provided)
[INFO] junit:junit:jar:3.8.2 (scope = test)
[INFO] log4j:log4j:jar:1.2.14 (scope = compile)
[INFO] org.apache.avalon.framework:avalon-framework-api:jar:4.3.1 (scope = compile)
[INFO] org.apache.avalon.framework:avalon-framework-impl:jar:4.3.1 (scope = compile)
[INFO] org.apache.cocoon:cocoon-configuration-api:jar:1.0.1-SNAPSHOT (scope = compile)
[INFO] org.apache.cocoon:cocoon-pipeline-api:jar:1.0.0-RC1-SNAPSHOT (scope = compile)
[INFO] org.apache.cocoon:cocoon-pipeline-impl:jar:1.0.0-RC1-SNAPSHOT (scope = compile)
[INFO] org.apache.cocoon:cocoon-sitemap-api:jar:1.0.0-RC1-SNAPSHOT (scope = compile)
[INFO] org.apache.cocoon:cocoon-spring-configurator:jar:1.0.1-SNAPSHOT (scope = compile)
[INFO] org.apache.cocoon:cocoon-thread-api:jar:1.0.0-RC1-SNAPSHOT (scope = compile)
[INFO] org.apache.cocoon:cocoon-util:jar:1.0.0-RC1-SNAPSHOT (scope = compile)
[INFO] org.apache.cocoon:cocoon-xml-api:jar:1.0.0-RC1-SNAPSHOT (scope = compile)
[INFO] org.apache.excalibur.components:excalibur-pool-api:jar:2.2.1 (scope = compile)
[INFO] org.apache.excalibur.components:excalibur-sourceresolve:jar:2.2.1 (scope = compile)
[INFO] org.apache.excalibur.components:excalibur-store:jar:2.2.1 (scope = compile)
[INFO] org.apache.excalibur.components:excalibur-xmlutil:jar:2.2.1 (scope = compile)
[INFO] org.apache.excalibur.containerkit:excalibur-instrument-api:jar:2.2.1 (scope = compile)
[INFO] org.apache.excalibur.containerkit:excalibur-logger:jar:2.2.1 (scope = compile)
[INFO] org.springframework:spring-aop:jar:2.0.3 (scope = compile)
[INFO] org.springframework:spring-beans:jar:2.0.3 (scope = compile)
[INFO] org.springframework:spring-context:jar:2.0.3 (scope = compile)
[INFO] org.springframework:spring-core:jar:2.0.3 (scope = compile)
[INFO] org.springframework:spring-web:jar:2.0.3 (scope = compile)
[INFO] xml-apis:xml-apis:jar:1.3.02 (scope = compile)
> 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
>
>
> 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
[jira] Updated: (MECLIPSE-262) Maven compilation and eclipse
classpath don't match with conflicting versions at same dependency depth
Posted by "Klaus Brunner (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Klaus Brunner updated MECLIPSE-262:
-----------------------------------
Attachment: testcase.zip
Test case (WAR project).
> 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
[jira] Updated: (MECLIPSE-262) Maven compilation and eclipse
classpath don't match with conflicting versions at same dependency depth
Posted by "Klaus Brunner (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Klaus Brunner updated MECLIPSE-262:
-----------------------------------
Attachment: screenshot-1.jpg
version conflict between eclipse and maven build (WAR project)
> 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, 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
[jira] Commented: (MECLIPSE-262) Maven compilation and eclipse
classpath don't match with conflicting versions at same dependency depth
Posted by "bob robertson jr (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138902#action_138902 ]
bob robertson jr commented on MECLIPSE-262:
-------------------------------------------
Another example. With maven 2.0.9 and version 2.5.1 of the eclipse plugin.
Our POM is:
{noformat}
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>com.org.net</groupId>
<artifactId>proofOfBrokenness</artifactId>
<version>1.0-SNAPSHOT</version>
<packaging>jar</packaging>
<dependencies>
<dependency>
<groupId>org.acegisecurity</groupId>
<artifactId>acegi-security</artifactId>
<version>1.0.4</version>
</dependency>
<dependency>
<groupId>commons-httpclient</groupId>
<artifactId>commons-httpclient</artifactId>
<version>3.1</version>
</dependency>
</dependencies>
</project>
{noformat}
Both artifacts have dependencies on commons-codec. One uses version 1.3, the other version 1.2.
Our eclipse project has a dependency on 1.2 whereas {{mvn dependency:tree}} reports v1.3.
This means that users check out the source code, populate the maven repository by compiling and then start up eclipse to see that not all the required libraries are in the repository.
> 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
> 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
[jira] Commented: (MECLIPSE-262) Maven compilation and eclipse
classpath don't match with conflicting versions at same dependency depth
Posted by "benson margulies (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=176874#action_176874 ]
benson margulies commented on MECLIPSE-262:
-------------------------------------------
p.s. I observed this with 2.6. It's unfortunate that us chickens don't have access to edit the field that states what version the problem has been observed in.
> 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
[jira] Commented: (MECLIPSE-262) Maven compilation and eclipse
classpath don't match with conflicting versions at same dependency depth
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94377 ]
Carlos Sanchez commented on MECLIPSE-262:
-----------------------------------------
I added plexus-component-api:1.0-alpha-24 to the parent pom dependency management section as a workaround
> 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
>
>
> 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
[jira] Commented: (MECLIPSE-262) Maven compilation and eclipse
classpath don't match with conflicting versions at same dependency depth
Posted by "Klaus Brunner (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Updated: (MECLIPSE-262) Maven compilation and eclipse
classpath don't match
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carlos Sanchez updated MECLIPSE-262:
------------------------------------
Attachment: eclipse.txt
compile.txt
debug output
> Maven compilation and eclipse classpath don't match
> ---------------------------------------------------
>
> 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
>
>
> 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
[jira] Commented: (MECLIPSE-262) Maven compilation and eclipse
classpath don't match
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94376 ]
Carlos Sanchez commented on MECLIPSE-262:
-----------------------------------------
i think the problem is that maven-core depends on
- plexus-container-default:1.0-alpha-24
- plexus-active-collections:1.0-beta-1
that in turn depend on plexus-container-api 1.0-alpha-24 and 1.0-alpha-19 respectively
so both are at same level, the problem so which one wins is undefined, but at lease eclipse and compiler plugin should behave the same
> Maven compilation and eclipse classpath don't match
> ---------------------------------------------------
>
> 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
>
>
> 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
[jira] Commented: (MECLIPSE-262) Maven compilation and eclipse
classpath don't match with conflicting versions at same dependency depth
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98875 ]
Carlos Sanchez commented on MECLIPSE-262:
-----------------------------------------
it may be caused because the eclipse plugin depend on maven 2.0.1 libraries, will need to update to 2.0.6 to see
> 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, 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
[jira] Commented: (MECLIPSE-262) Maven compilation and eclipse
classpath don't match with conflicting versions at same dependency depth
Posted by "Chad Wilson (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208161#action_208161 ]
Chad Wilson commented on MECLIPSE-262:
--------------------------------------
The core issue here still happens with maven-eclipse-plugin 2.7, under Maven 2.2.1, FWIW. If I understand correctly from the Dependency Mediation Section of [Introduction to the Dependency Mechanism|http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Transitive_Dependencies], from Maven 2.0.9+ such a conflict at the same depth should be resolved by choosing the version from the parent which is first declared in your pom.xml.
I think it was indeterminate from Maven's perspective before that point so I'm not so surprised that this bug was logged against Maven 2.0.6, however now there's a rule, so the Eclipse plugin should surely behave consistently with the dependency plugin (if it cannot share the source, as I read from MECLIPSE-472).
> 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
[jira] Commented: (MECLIPSE-262) Maven compilation and eclipse
classpath don't match with conflicting versions at same dependency depth
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99108 ]
Carlos Sanchez commented on MECLIPSE-262:
-----------------------------------------
Upgraded maven dependencies,will see if this solves the problem
> 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, 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
[jira] Commented: (MECLIPSE-262) Maven compilation and eclipse
classpath don't match with conflicting versions at same dependency depth
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98907 ]
Carlos Sanchez commented on MECLIPSE-262:
-----------------------------------------
Klaus, with Maven 2.0.6 I get the same commons-collections in both places
> 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, 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
[jira] Updated: (MECLIPSE-262) Maven compilation and eclipse
classpath don't match with conflicting versions at same dependency depth
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carlos Sanchez updated MECLIPSE-262:
------------------------------------
Summary: Maven compilation and eclipse classpath don't match with conflicting versions at same dependency depth (was: Maven compilation and eclipse classpath don't match)
> 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
>
>
> 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
[jira] Commented: (MECLIPSE-262) Maven compilation and eclipse
classpath don't match with conflicting versions at same dependency depth
Posted by "benson margulies (JIRA)" <ji...@codehaus.org>.
[ 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