[
https://issues.apache.org/jira/browse/AMQ-6585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher L. Shannon resolved AMQ-6585.
-----------------------------------------
Resolution: Fixed
I believe this is finally fixed now. Because AMQ-6576 embedded Spring xbean
already I was able to upgrade to 2.18.x by using the camel-blueprint feature
and dropping the old Spring DM stuff as that was requiring Spring 3.2 still. I
also bumped the version range for our Spring dependency to 4.
I've re-enabled the Camel tests under the karaf-itest project and everything is
passing again.
> Upgrade to Camel 2.18.x
> -----------------------
>
> Key: AMQ-6585
> URL: https://issues.apache.org/jira/browse/AMQ-6585
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker, OSGi/Karaf
> Reporter: Christopher L. Shannon
> Assignee: Christopher L. Shannon
> Fix For: 5.15.0
>
>
> Now that ActiveMQ version 5.15.0 is going to be Java 8 we can upgrade to the
> latest version of Camel 2.18.x. The biggest challenge here is the OSGi
> portion as it will break because the new version of Camel was refactored a
> bit and spring dm was moved into its own module, etc. One issue I noticed is
> that Spring-xbean causes a problem because it still relies on Spring 3.2.x.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
