We have the same situation.
Include the Spring that you need directly in a dependency in the POM and
use exclusions on all versions of Spring in the dependencies that are
transitively bringing in 2.0.x that you do not want.
Ron
On 18/05/2010 12:54 PM, C. Benson Manica wrote:
I have a project which depends on artifacts which transitively depend on
different Spring versions. I need to manually exclude all spring*-2.0.8
artifacts from being included in the project, since they don't play nicely
with the 2.5 artifacts. How do I do this? The documentation has led me to
believe that
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<version>2.1</version>
<configuration>
<!-- Try to prevent the spring security libs at 2.0 from
dragging in old spring core libs -->
<excludeArtifactIds>
org.springframework.spring-core,org.springframework.spring-support,org.springframework.spring-context
</excludeArtifactIds>
<excludeTransitive>true</excludeTransitive>
</configuration>
</plugin>
would work, but it doesn't - mvn dependency:resolve on a clean repository
still shows lines like
Downloading:
http://ide-svn.turner.com/artifactory/repo/org/springframework/spring-context/2.0.8/spring-context-2.0.8.pom
What am I doing wrong?
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
