CAS 3.2 trunk version Spring dependency collision when using Artifactory Maven2 Proxy

[Robert Oschwald]

We had a problem here to build the current CAS trunk version.
We had duplicate Spring artifact versions, 2.5.1 and version 2.0.6 for
spring-context, spring-webapp and spring-core if we use our internal
Artifactory server 1.2.5 with maven 2.0.8.
 
To solve this, we added DependencyManagement to the main pom.xml:
 
 <dependencyManagement>
  <!-- ensure only the propper artifact versions are used -->
  <dependencies> 
   <dependency>
    <groupId>commons-collections</groupId>
    <artifactId>commons-collections</artifactId>
    <version>3.2</version>
   </dependency> 
   <dependency>
    <groupId>org.springframework</groupId>
    <artifactId>spring-beans</artifactId>
    <version>2.5.1</version>
   </dependency> 
   <dependency>
    <groupId>org.springframework</groupId>
    <artifactId>spring-core</artifactId>
    <version>2.5.1</version>
   </dependency> 
   <dependency>
    <groupId>org.springframework</groupId>
    <artifactId>spring-context</artifactId>
    <version>2.5.1</version>
   </dependency>
   <dependency>
    <groupId>org.springframework</groupId>
    <artifactId>spring-web</artifactId>
    <version>2.5.1</version>
   </dependency>
  </dependencies>
 </dependencyManagement>
 
Maybe it would be a good solution to include dependencyManagement to the
trunk version to ensure only the propper artifacts are taken.
 
 
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://tp.its.yale.edu/pipermail/cas/attachments/20080314/da618c34/attachment.html