Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
None
-
None
-
Unknown
Description
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:
<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>
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:
<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>
whereas the current netty deps used by the client are actually:
netty-buffer netty-common netty-handler netty-transport netty-codec netty-codec-http