You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Christopher L. Shannon (JIRA)" <ji...@apache.org> on 2017/06/09 11:13:18 UTC
[jira] [Assigned] (AMQ-6585) Upgrade to Camel 2.18.x
[ https://issues.apache.org/jira/browse/AMQ-6585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christopher L. Shannon reassigned AMQ-6585:
-------------------------------------------
Assignee: Christopher L. Shannon
> 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)