activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-6585) Upgrade to Camel 2.18.x
Date Fri, 09 Jun 2017 11:16:18 GMT

    [ https://issues.apache.org/jira/browse/AMQ-6585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16044315#comment-16044315
] 

ASF subversion and git services commented on AMQ-6585:
------------------------------------------------------

Commit a6782443c1695f54176afecfda6c5c423bc18a84 in activemq's branch refs/heads/master from
[~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=a678244 ]

AMQ-6585 - Upgrade to Camel 2.18.4

Added the camel-blueprint feature to work with Spring 4.x as Spring DM
support for Camel was deprecated


> 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)

Mime
View raw message