Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Thu, 18 Dec 2014 14:04:13 +0000 (UTC)
From: "metatech (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12757938.1416996907000.57298.1418911453576@Atlassian.JIRA>
In-Reply-To: <JIRA.12757938.1416996907000@Atlassian.JIRA>
References: <JIRA.12757938.1416996907000@Atlassian.JIRA>
 <JIRA.12757938.1416996907451@arcas>
Subject: [jira] [Commented] (CAMEL-8080) Make Camel CXF dependency on Camel
 Spring optional
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

metatech commented on CAMEL-8080:
---------------------------------

Please note, however, Camel-JMS uses Spring Framework JMS support, even in a Blueprint bundle.  This means that any bundle using queues transitively uses Spring, and that Spring cannot be uninstalled from the container.

> Make Camel CXF dependency on Camel Spring optional
> --------------------------------------------------
>
>                 Key: CAMEL-8080
>                 URL: https://issues.apache.org/jira/browse/CAMEL-8080
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-cxf
>    Affects Versions: 2.10.7
>         Environment: ServiceMix 4.5.3
>            Reporter: metatech
>            Assignee: Willem Jiang
>             Fix For: 2.15.0
>
>         Attachments: camel_cxf_spring_optional.patch
>
>
> By default, Camel-CXF depends on Camel-Spring, which prevents a ServiceMix installation using only Blueprint bundles from uninstalling Camel-Spring altogether.
> Here is a patch that makes Spring optional in Camel CXF dependencies, both in OSGi imports and within the Karaf feature.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)