This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.

Comment

I've not tried this yet, but is it possible that the Jersey dependency is transitively drawing in some older version of Spring, confusing the classpath with multiple versions of Spring? I've had this kind of thing happen before and it was a simple (although annoying) matter of adding in some exclusions to keep out the transitive dependencies.

Okay, I take that back...I just tried it and it looks like the Jersery dependency is pulling in Spring 2.5.6 dependencies along with the Spring 3.1 (SNAPSHOT) dependencies and thereby confusing the classpath with multiple versions of Spring. (It seems that the 2.5.6 final dependencies trump the 3.1 snapshot dependencies.)

I changed the dependency to look like the following and it built fine: