Hi,
I'm trying to run eclipse:eclipse for a sample project but it seems that
the plugin resolves the dependency incorrectly. Below are the details:
I have defined dependecies in my pom to projects that transitively
depend on commons-digester, one on version 1.6 and the other on version
1.8. I do not include any direct dependencies on commons-digester in my
pom.xml The problem is that when the eclipse:eclipse goal is run it
generates the .classpath that includes version 1.6 of commons-digester.
However when I run dependency:resolve it shows that my project depends
on version 1.8 of the library.
When I use
<dependencyManagement>
< dependencies>
<dependency>
<groupId>commons-digester</groupId>
<artifactId>commons-digester</artifactId>
<version>[1.8,)</version>
</dependency>
</dependencies>
</dependencyManagement>
there are no changes and the .classpath still includes version 1.6
When I use
<dependencyManagement>
< dependencies>
<dependency>
<groupId>commons-digester</groupId>
<artifactId>commons-digester</artifactId>
<version>1.8</version>
</dependency>
</dependencies>
</dependencyManagement>
the .classpath includes the correct 1.8 version.
Nonetheless I probably should see version 1.8 without
<dependencyManagement /> if dependency:resolve shows that the projects
depends on version 1.8, should I not?
If it's a bug and it hasn;t yet been filed please let me know and I'll
create a ticket for it.
Regards,
Tom
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
