I'm running CAS 4.1.3 and using the maven overlay from: https://github.com/Jasig/cas-overlay-template and I'm running into a problem where my resulting war file contains multiple versions of the same jar file. There are a few cases of this but the one giving me trouble right now is spring-core.
person-directory-impl-1.7.1 brings in spring-context-4.2.4.RELEASE which of course leads to spring-core-4.2.4.RELEASE. However I'm finding that my resulting war also contains spring-core-4.1.8.RELEASE. I've tried adding a block to resolve this collision: <dependencyManagement> <dependencies> <dependency> <groupId>org.springframework</groupId> <artifactId>spring-core</artifactId> <version>4.2.4.RELEASE</version> </dependency> </dependencies> </dependencyManagement> but it seems to have no effect. I noticed that cas-server-webapp-4.1.3.war contains spring-core-4.1.8.RELEASE. Is the cop of spring-core-4.1.8 that ultimately ends up in my war coming from thie cas-server-webapp-4.1.3.war and not the maven dependency tree? This would explain why my dependencyManagement block had no effect. If this is the case, how to I keep old versions of the colliding jars that are a part of the base war dependency from showing up in my final war built by the overlay task? Thanks -- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/a/apereo.org/group/cas-user/.
