Affects Version/s: None
Fix Version/s: 2.0
KULRICE-3973 Spring 3.0.1 and module beans KULRICE-6306 Upgrade Spring version to 3.1.0.RELEASE KULRICE-11635 Analyze upgrade to Spring 4.x KULRICE-12865 Upgrade to Spring 4.0.5 KULRICE-12879 Pom.xml file cleanup from Spring 4 upgrade KULRICE-6514 Upgrade to "spring-security-cas" version 3.1.0.RELEASE KULRICE-14144 Re-upgrade Rice to Spring 4 KULRICE-9731 Upgrade Rice to the latest version of the Spring Framework 3.2.x KULRICE-12880 Apply Spring 4.0.5 upgrade KULRICE-4418 cxf upgrade causes incorrect spring version to be brought in in client applications.
This was discussed at the TRC. We decided to go ahead and test out an upgrade to Spring 2.5 to see if it causes any issues and then determine from there if we will move ahead with the upgrade.
Here are Scott's notes on the subject.
Here are the spring 2.0.x -> 2.5.x jar changes I was supposed to send out
after the last meeting.
spring-dao -> spring-tx
spring-jpa -> spring-orm
spring-remoting/rmi -> spring-context
spring-remoting/the_rest -> spring-web
spring-support /instrument,scripting -> spring-context
spring-support/the_rest -> spring-context-support
spring-mock -> spring-test
In KS we either overlay the rice war or depend on the rice-impl, so I
don't have actual rice pom changes. We had been excluding spring-dao and
spring-jpa and have -tx and -orm in our depends already. I noticed
remoting, support and mock were still 2.0.x in our projects so I dug up
where they moved to.