Hi,
I suspect this is due to the eclipse plugin handling dependency
resolution itself (see method doDependencyResolution() in [1]) instead
of using the maven build-in one.
You should file a jira issue in the eclipse-plugin [1] for this, as both
mechanisms should resolve to the same dependency versions. It's best
practice to provide a small test project that shows the bug, so the
developers can reproduce it more easily.
Wait... there is already a bug filed for this [3].
-Tim
[1]
https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-eclipse-plugin/src/main/java/org/apache/maven/plugin/ide/AbstractIdeSupportMojo.java
[2] http://jira.codehaus.org/browse/MECLIPSE
[3] http://jira.codehaus.org/browse/MECLIPSE-262
Lewandowski, Eric schrieb:
Hi,
I use Maven 2.0.7 with JDK 1.5.0_12 on Windows XP.
My application use struts2 and spring-framework.
In my POM, I add the dependency : org.springframework:spring-beans:2.0.1
and the dependency org.apache.struts:struts2-spring-plugin:2.0.9
I run mvn eclipse:clean eclipse:eclipse -Dwtpversion=1.5
In Eclipse, I see the dependency org.springframework:spring-beans:2.0.5 because
org.apache.struts:struts2-spring-plugin:2.0.9 needs this dependency
I run mvn clean package. My war file contains
org.springframework:spring-beans:2.0.1 (not 2.0.5) because I specified it in my
pom.
Is it normal the de dependency computation is different between mvn
eclipse:eclipse and mvn package ?
May I do some errors in my maven configuration ? (pom, settings).
Regards,
Eric Lewandowski
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
