[
https://issues.apache.org/jira/browse/AMQ-6585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16050849#comment-16050849
]
ASF subversion and git services commented on AMQ-6585:
------------------------------------------------------
Commit 6b9883f10f6c5d1468e67924aeb37ec7d9d48554 in activemq's branch
refs/heads/master from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=6b9883f ]
AMQ-6585 - update to Camel 2.19.1
> 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.4.14#64029)
