[jira] [Commented] (AMQ-4909) OSGi granularity of activemq-osgi bundle

["Arthur Naseef (JIRA)" <ji...@apache.org>]

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

Arthur Naseef commented on AMQ-4909:
------------------------------------

Git commits:
https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=26c41d0362d9f4bf27568e6ce7fcfd7e2e59fde8

https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=e64da4a71fd3d5d1e9b59a62727af72ee577e8bf

> OSGi granularity of activemq-osgi bundle
> ----------------------------------------
>
>                 Key: AMQ-4909
>                 URL: https://issues.apache.org/jira/browse/AMQ-4909
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: OSGi/Karaf
>    Affects Versions: 5.9.0
>            Reporter: Raúl Kripalani
>            Assignee: Dejan Bosanac
>             Fix For: 5.9.1, 5.10.0
>
>
> Installing any AMQ feature, whether activemq-client, activemq-broker or activemq-camel, ends up installing the activemq-osgi bundle which is a one-stop-shop include-all bundle for AMQ.
> In other words, if you install activemq-client you end up with a fully fledged broker. If you install activemq-camel, you also end up with a fully fledged broker.
> Moreover, the AMQ Camel component is part of the activemq-osgi bundle, which means that you can no longer upgrade only the AMQ broker if you're running in a setup with Camel, because it drags along an updated Camel AMQ component which may require newer Camel APIs. 
> At least it's not possible via Karaf features. A workaround may be to fall back to installing individual AMQ bundles.
> More info here: http://activemq.2283324.n4.nabble.com/Upgrading-only-AMQ-broker-in-OSGi-container-with-Camel-tp4674930.html.



--
This message was sent by Atlassian JIRA
(v6.2#6252)