Module "cas-server-webapp-support" pulls in stale Spring dependencies that crash CAS
Description
If you include the "cas-server-webapp-support" module in a WAR overlay project it pulls in Spring modules from version 3.0.x or which is incompatible with the Spring 3.2.2 modules pulled in by the rest of CAS.
When you launch the CAS webapp it fails to initialize and the logs are filled with NoSuchMethod or NoSuchField exceptions. The exact errors seem to depend on what other dependencies you might have included, as other modules could pull in newer Spring JARs and mask the problem partially or fully.
Attached is a minimal test case to reproduce the problem. Put the attached pom.xml in a new directory, then run "mvn package" and put the resulting WAR in a vanilla Tomcat instance configured for HTTPS.
Attached is a Tomcat log file containing the errors produced by the above test case on my machine.
Could you update the dependencies of "cas-server-webapp-support" before 4.0 is out?
As far as I can tell, the parent pom is already exacting the versions in the dependency management block. Is that what you are looking for?
Ivan Todoroski November 1, 2013 at 8:16 PM
End users can temporarily work around this issue by including the following in their pom.xml (exact list of dependency overrides might vary depending on what other dependencies you might have):
If you include the "cas-server-webapp-support" module in a WAR overlay project it pulls in Spring modules from version 3.0.x or which is incompatible with the Spring 3.2.2 modules pulled in by the rest of CAS.
When you launch the CAS webapp it fails to initialize and the logs are filled with NoSuchMethod or NoSuchField exceptions. The exact errors seem to depend on what other dependencies you might have included, as other modules could pull in newer Spring JARs and mask the problem partially or fully.
Attached is a minimal test case to reproduce the problem. Put the attached pom.xml in a new directory, then run "mvn package" and put the resulting WAR in a vanilla Tomcat instance configured for HTTPS.
Attached is a Tomcat log file containing the errors produced by the above test case on my machine.
Could you update the dependencies of "cas-server-webapp-support" before 4.0 is out?