Both camel-core and camel-spring declare dependencies on the fully bundled "spring" jar.
This precludes using spring-javaconfig-1.0m3-snapshot (or any other similar project) because it declares dependencies on the smaller unbundled jars like "spring-context" and the project winds up with multiple copies of the same classes, and in the worst case, even with different versions of the same classes. I don't know if this just reveals that I don't understand maven fully, or if it is a real problem. But, I suspect the osgi support in both spring and camel will also be improved by using the unbundled jars. Can camel switch to declaring dependencies on the unbundled jars? Also, I don't know if the changes made between 2.0 and 2.1/2.5 have any impact on camel switching to the unbundled jars. But here is a link that outlines them. http://blog.interface21.com/main/2007/06/01/infrastructure-changes-in-spring-21-m2/ thanks in advance, Steven Marcus -- View this message in context: http://www.nabble.com/pom-dependency-on-%22spring%22-instead-of-%22spring-context%22-et-al.-tp14475572s22882p14475572.html Sent from the Camel - Users mailing list archive at Nabble.com.
