Alex, It looks like spring-security-cas-client 2.0.4 references cas-client-core 3.1.3. Maven appears to follow the dependency rules correctly here. You could probably add an exclusion for it.
I remember running into an issue of duplicate cas client jar files (different revisions) when building CAS 3.3.5 using Maven overlay. I didn't pursue this, as time was precious at the time. With Maven overlay it is more difficult to trace Maven dependency issues (I am spoiled by the Eclipse Maven plugin). I think that a posting on this list had a suggestion for a fix, but I don't remember what that was. Do you know what's pulling in cas-client-core 3.1.9 jar into your project? Adam Alex Barker wrote: > Maven appears to be magically adding dependencies as it sees fit. > Despite my best efforts the cas-client-core-3.1.3.jar keeps ending up in > my WAR file yet that version is not defined anywhere in any pom. I also > get the cas-client-core-3.1.9.jar version which I assume is the correct > version for cas 3.3.5. The only place I can even find that version of > the cas java client is in the pre built > /cas-server-3.3.5/modules/cas-server-webapp-3.3.5.war file. > > Can someone please explain how this file keeps ending up in my custom > built cas.war overlay? > > Alexander Barker > Senior Programmer > California Lutheran University > Information Systems and Services > 60 West Olsen Road > Thousand Oaks, CA 91360 > 805.493.3912 > > > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
<<attachment: arybicki.vcf>>
