activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ioannis Canellos (JIRA)" <>
Subject [jira] [Updated] (AMQ-4341) activemq-broker feature can not be installed when OBR is enabled
Date Tue, 26 Feb 2013 18:38:12 GMT


Ioannis Canellos updated AMQ-4341:

    Attachment: AMQ-4341-2.patch

I am attaching a second cut of the initial patch.

This patch adopts Gerts suggestion about being explicit on some package imports, so that we
avoid having issues with the resolver.

The patch also adds some missing depedencies from the features descriptor and removes features
that have no longer value (activemq-http).

It also adds an itest that checks the activemq-client feature against obr.

Last but not least, it modifies the activemq-osgi headers so that it depends as less as possible
on dynamic-imports. Added some explict imports and also added some optional imports for dependencies
that are not used at all by the client.
> activemq-broker feature can not be installed when OBR is enabled
> ----------------------------------------------------------------
>                 Key: AMQ-4341
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Task
>    Affects Versions: 5.8.0
>            Reporter: Gert Vanthienen
>            Assignee: Gary Tully
>         Attachments: AMQ-4341-2.patch, AMQ-4341.patch
> While trying to integrate ActiveMQ 5.8.0 into ServiceMix 5.0.0, I bumped into 2 problems
with the features descriptor on a Karaf-based container that has OBR resolution enabled for
the Features service:
> * the activemq-http fragment is referring to a Fragment-Host called {{org.apache.activemq.activemq-core}},
which no longer exists
> * the xbean-spring bundle is marked with {{dependency=true}} but no other bundle is importing
any packages from it, so it does not get installed - since {{activemq-karaf}} does need those
packages to work properly, the easiest solution is probably to add a proper Import-Package
header to that bundle.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message