You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/06/17 21:00:08 UTC

[jira] [Commented] (AMQ-6328) Upgrade Camel to latest

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

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

Commit 0afe7d9d2401ee902ec4a7ca18146cd9c29ef55e in activemq's branch refs/heads/activemq-5.13.x from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=0afe7d9 ]

https://issues.apache.org/jira/browse/AMQ-6328

Update camel to 2.16.3

> Upgrade Camel to latest
> -----------------------
>
>                 Key: AMQ-6328
>                 URL: https://issues.apache.org/jira/browse/AMQ-6328
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: activemq-camel
>    Affects Versions: 5.13.3
>            Reporter: Kevan Simpson
>
> There is a showstopper (for us) bug in Camel 2.16.2: https://issues.apache.org/jira/browse/CAMEL-9672
> It's confirmed fixed in 2.16.3 (or 2.17.0).  Can one of these latest be introduced to ActiveMQ please?  Thanks!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)