[
https://issues.apache.org/jira/browse/AMQ-6585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850188#comment-15850188
]
Christopher L. Shannon commented on AMQ-6585:
---------------------------------------------
I figure for spring-xbean we might just want to embed it as it seems to be a
dead project. It might be good enough just to use the maven shade plugin to
include the classes we need inside one of our packaged jars.
I think moving Camel over might be a good long term goal but I would suspect
some people are probably using the plugin and would complain if removed so a
deprecation approach before removal is probably a good idea.
> 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
> 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)
