[
https://issues.apache.org/jira/browse/AMQ-4341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13584430#comment-13584430
]
Gary Tully commented on AMQ-4341:
---------------------------------
currently there is one uber bundle, activemq-osgi that contains activemq-http,
activemq-spring along with the broker,client etc. So an all in one shop.
The activemq-http feature may need to disappear, but at a minimim it should not
pull in the activemq-http bundle. This is the cause of the broken features.
With the uber bundle, all other bundles could disappear, but i think it makes
sense to allow more modular deployment once we have tests for each.
So we need to fix the issues with the metadata to allow more flexibility of
deployment.
btw: the OBR resolution must be the reason this was not caught by the
activemq-karaf-itest
> activemq-broker feature can not be installed when OBR is enabled
> ----------------------------------------------------------------
>
> Key: AMQ-4341
> URL: https://issues.apache.org/jira/browse/AMQ-4341
> Project: ActiveMQ
> Issue Type: Task
> Affects Versions: 5.8.0
> Reporter: Gert Vanthienen
>
> 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: http://www.atlassian.com/software/jira
