I have what I believe was the same problem although I saw slightly different symptoms.
Using m2eclipse with the 3.3.3 release, there is an artifact version conflict between the versions of Spring called up directly in the POMs and the version referenced indirectly through an included dependency. The dependency POM specifically declared itself dependent on a Spring 2.0 version while CAS is dependent on 2.5. This is apparently not a problem for the Maven build, which uses the latest and greatest version of the artifact. However, m2eclipse follows a different algorithm to build the Maven Dependencies list for the Eclipse Build Path, and it ends up adding both the 2.0.7 and 2.5.6 Jars to the list. When it goes to deploy/test/debug the application, unfortunately the 2.0 JAR comes first in alphabetic order and gets searched before the 2.5. I could have tried to rewrite some third party POM to fix the problem, but that seemed too complicated. The brute force solution, but very messy, is to delete the 2.0 JAR from the WEB-INF/lib before running the generated Web application. However, this does not exactly match the description below. When both JARs are included, you end up getting methods and fields not found because you pick up an old copy of a Class from the 2.0 JAR and then try to call a 2.5 only method. The symptom you are reporting would occur if m2eclipse copied only the 2.0 JAR into WEB-INF lib instead of copying both and having 2.0 get processed first. -----Original Message----- I try to build cas server 3.3.3 with m2eclipse plugin. When the war file is built an invalid version of spring-core and spring-beans libraries is used producing ClassNotFoundException at runtime. -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
