activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arthur Naseef (JIRA)" <>
Subject [jira] [Commented] (AMQ-4909) OSGi granularity of activemq-osgi bundle
Date Sat, 07 Jun 2014 20:36:02 GMT


Arthur Naseef commented on AMQ-4909:

Git commits:;a=commit;h=26c41d0362d9f4bf27568e6ce7fcfd7e2e59fde8;a=commit;h=e64da4a71fd3d5d1e9b59a62727af72ee577e8bf

> OSGi granularity of activemq-osgi bundle
> ----------------------------------------
>                 Key: AMQ-4909
>                 URL:
>             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
> 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:

This message was sent by Atlassian JIRA

View raw message