If I declare a dependency on Spring 1.2.6 and a project that depends
on Spring 1.2.5...
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring</artifactId>
<version>1.2.6</version>
</dependency>
<dependency>
<groupId>org.apache.shale</groupId>
<artifactId>shale-spring</artifactId>
<version>1.0.0-SNAPSHOT</version>
</dependency>
where shale-spring depends on the 'old' groupId of springframework:
<dependency>
<groupId>springframework</groupId>
<artifactId>spring</artifactId>
<version>1.2.5</version>
</dependency>
Then I get both Spring jars in WEB-INF/lib.
In this case, I'm in control of both build files, so I can fix it, but
that will not always be the case. Shouldn't Maven be able to figure
out that springframework was relocated to org.springframework (or the
other way around) and deal with it?
Thanks,
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
