Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CEF1A10BC7 for ; Thu, 12 Dec 2013 09:18:12 +0000 (UTC) Received: (qmail 44087 invoked by uid 500); 12 Dec 2013 09:18:12 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 43572 invoked by uid 500); 12 Dec 2013 09:18:08 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 43154 invoked by uid 99); 12 Dec 2013 09:18:07 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Dec 2013 09:18:07 +0000 Date: Thu, 12 Dec 2013 09:18:07 +0000 (UTC) From: "Richard Kettelerij (JIRA)" To: dev@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMQ-4909) OSGi granularity of activemq-osgi bundle MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMQ-4909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846184#comment-13846184 ] Richard Kettelerij commented on AMQ-4909: ----------------------------------------- This is definitely a step in the right direction, thanks [~dejan_b@datagate.co.yu]! Although I don't think the issue is entirely resolved. The activemq-camel feature still depends on the activemq-client feature which IMHO is too heavyweight. This is primarily due to the large/uber activemq-osgi bundle included in the activemq-client feature. > 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: Raul Kripalani > Assignee: Dejan Bosanac > Fix For: 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.1.4#6159)