[
https://issues.apache.org/jira/browse/CAMEL-4778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13236535#comment-13236535
]
David Valeri commented on CAMEL-4778:
-------------------------------------
I did a little more digging and it turns out that my earlier conclusion was
based on some bad observations in Eclipse. It turns out that the only real
issue is how Maven wants to do the build. Maven wants one version of Spring on
the classpath. If we implement the new method needed to move to Spring 3.1,
the camel-spring-test library compiled against 3.1 will work with client code
using Spring 3.0 on its classpath. This binary compatibility for client code
means that the only issue is compiling the Spring 3.1 compatible
camel-spring-test JAR against the Spring 3.0 JARs. This feat won't be possible
due to the aforementioned Maven behavior.
We need a way to compile the camel-test-spring module against Spring 3.1 but
run the tests against Spring 3.1 and Spring 3.0. I can think of some ways to
achieve that, but they are a little bit messy. Is there a clean way to get
Maven to support this use case?
We also need to update the documentation to say from 2.11 or 3.0 onwards or
export the documentation for later use. The Camel 3 stuff is still up in the
air so do you have a roadmap for Spring 3.0 support deprecation?
> Upgrade Spring to 3.1.1.RELEASE
> -------------------------------
>
> Key: CAMEL-4778
> URL: https://issues.apache.org/jira/browse/CAMEL-4778
> Project: Camel
> Issue Type: Task
> Affects Versions: 2.8.3, 2.9.0
> Reporter: Christian Müller
> Assignee: Christian Müller
> Labels: spring
>
> We should consider to upgrade to Spring 3.1.0.RELEASE in Camel 2.10.0 or
> 3.0.0 depending on the backwards compatibility of Spring.
> See: http://static.springsource.org/spring/docs/3.1.0.RELEASE/changelog.txt
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
