camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robbie Gemmell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-10369) update camel-amqp to use qpid-jms-client-0.11.1
Date Wed, 18 Jan 2017 12:04:26 GMT

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

Robbie Gemmell commented on CAMEL-10369:
----------------------------------------

For what its worth a newer 0.20.0 release is currently under vote, though it moves to JMS
2.0 as well.

> update camel-amqp to use qpid-jms-client-0.11.1
> -----------------------------------------------
>
>                 Key: CAMEL-10369
>                 URL: https://issues.apache.org/jira/browse/CAMEL-10369
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-amqp
>            Reporter: Robbie Gemmell
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.19.0
>
>
> The 0.11.1 release of Qpid JMS client is now out. It adds OSGi metadata thanks to a PR
from https://github.com/ctron.
> I'm not familiar with karaf at all but I see use of the 'qpid-jms-client-version' and
'qpid-proton-j-version' properties from parent/pom.xml in platforms/karaf/features/src/main/resources/features.xml:
> {noformat}
>     <bundle dependency='true'>wrap:mvn:org.apache.qpid/qpid-jms-client/${qpid-jms-client-version}</bundle>
>     <bundle dependency='true'>wrap:mvn:org.apache.qpid/proton-j/${qpid-proton-j-version}</bundle>
> {noformat}
> If I understand correctly that is 'wrapping' them with OSGi details due to them not previously
having any themselves, in which case wrapping may no longer be required given qpid-jms-0.11.1
and proton-j 0.13.0 adding OSGi metadata.
> In the same bit, I see the following netty bits listed:
> {noformat}
>     <bundle dependency='true'>mvn:io.netty/netty-resolver/${netty-version}</bundle>
>     <bundle dependency='true'>mvn:io.netty/netty-common/${netty-version}</bundle>
>     <bundle dependency='true'>mvn:io.netty/netty-buffer/${netty-version}</bundle>
>     <bundle dependency='true'>mvn:io.netty/netty-transport/${netty-version}</bundle>
>     <bundle dependency='true'>mvn:io.netty/netty-handler/${netty-version}</bundle>
>     <bundle dependency='true'>mvn:io.netty/netty-transport-native-epoll/${netty-version}</bundle>
>     <bundle dependency='true'>mvn:io.netty/netty-codec/${netty-version}</bundle>
> {noformat}
> whereas the current netty deps used by the client are actually:
> {noformat}
> netty-buffer
> netty-common
> netty-handler
> netty-transport
> netty-codec
> netty-codec-http
> {noformat}



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

Mime
View raw message