Return-Path: 
 <dev-return-5643-apmail-karaf-dev-archive=karaf.apache.org@karaf.apache.org>
X-Original-To: apmail-karaf-dev-archive@minotaur.apache.org
Delivered-To: apmail-karaf-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id CD6C2E209
	for <apmail-karaf-dev-archive@minotaur.apache.org>;
 Wed, 27 Feb 2013 07:17:58 +0000 (UTC)
Received: (qmail 94741 invoked by uid 500); 27 Feb 2013 07:17:58 -0000
Delivered-To: apmail-karaf-dev-archive@karaf.apache.org
Received: (qmail 94370 invoked by uid 500); 27 Feb 2013 07:17:57 -0000
Mailing-List: contact dev-help@karaf.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@karaf.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@karaf.apache.org>
List-Post: <mailto:dev@karaf.apache.org>
List-Id: <dev.karaf.apache.org>
Reply-To: dev@karaf.apache.org
Delivered-To: mailing list dev@karaf.apache.org
Received: (qmail 94330 invoked by uid 99); 27 Feb 2013 07:17:56 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Feb 2013 07:17:56 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of krzys.sobkowiak@gmail.com
 designates 209.85.217.178 as permitted sender)
Received: from [209.85.217.178] (HELO mail-lb0-f178.google.com)
 (209.85.217.178)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Feb 2013 07:17:48 +0000
Received: by mail-lb0-f178.google.com with SMTP id n1so261395lba.9
        for <multiple recipients>; Tue, 26 Feb 2013 23:17:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:x-received:in-reply-to:references:date:message-id
         :subject:from:to:cc:content-type;
        bh=TKZK+JSXlxc4hzO74mjJIWLtKq7YWYBQP2sMKdmGtaE=;
        b=dTc+txOuZ1s8NEnm25KtoLnk7obPEMk+I4EYpEkkbjurAhNK8E3MZVMLfOhxfXCSA5
         g7xV1JSl5qKukDL+30GTWl52sCr7/lRn+FNyiQKPVwEKFNDPjS+OsvqRnJZDR9oNjaUP
         cCim0um4b8EsidSQ1qAEMfBUX9zYZhAWjIpZIwRsL5+a3AzbBwDgJbTQMBe9I9Af841w
         VLZkF4zDUEqDFsgdNQT5nh4StxMispN009lsuy5woE088x4sEFwVT1cYlZjep1ONTlZr
         7Z1/osQbQpDRsy939Lbd2c/EZ70xky6XkkGhKEZx8p1z6pRcE/QjjFuwz+FOYbPKWmla
         8Jrg==
MIME-Version: 1.0
X-Received: by 10.152.123.194 with SMTP id mc2mr1067986lab.7.1361949448072;
 Tue, 26 Feb 2013 23:17:28 -0800 (PST)
Received: by 10.112.57.180 with HTTP; Tue, 26 Feb 2013 23:17:27 -0800 (PST)
In-Reply-To: 
 <CAK--DP-cNvYh8y5eTaAep_JKj+HsY3gg_rdHfM82sTh7nbMQaQ@mail.gmail.com>
References: <1361632500016-4027864.post@n3.nabble.com>
	<512A4900.6090704@nanthrax.net>
	<1361879755658-4027884.post@n3.nabble.com>
	<CAK--DP-cNvYh8y5eTaAep_JKj+HsY3gg_rdHfM82sTh7nbMQaQ@mail.gmail.com>
Date: Wed, 27 Feb 2013 08:17:27 +0100
Message-ID: 
 <CAFqgEbgzWfU4UUNdwxTEhQVXUEyXZHKT9F68EjS8wmCBD2qnrw@mail.gmail.com>
Subject: Re: New Karaf features on github
From: Krzysztof Sobkowiak <krzys.sobkowiak@gmail.com>
To: user@karaf.apache.org
Cc: dev@karaf.apache.org
Content-Type: multipart/alternative; boundary=f46d04426eda0df66e04d6af912a
X-Virus-Checked: Checked by ClamAV on apache.org

--f46d04426eda0df66e04d6af912a
Content-Type: text/plain; charset=ISO-8859-1

Hi

Perhaps we should have a separate subproject/repository for the enterprise
features. The wouldn't block Karaf releases but could be updated after a
new Karaf version is released (e.g. if the enterprise features need some
dependencies included in standard Karaf features) or after a new enterprise
library is released. Another solution would be such a repository as a SMX
subproject. There is already repository for osgifying external bundles
(Could be there committed any osgified libraries or should they be
compatible with Apache license?). There could be something similar for
enterprise features.

In my opinion the current Karaf enterprise features repository should still
be part of Karaf as it is a integral part of Karaf and many other features
depend on them. I mean we could have a separate subproject for any other
3rd party enterprise libraries which other users could use in their
projects.

I don't know whether all  eterprise libraries fulfill  the rules to be
dependencies of Apache project. If no, It could be only a Github project.

Regards
Krzysztof

On 27 February 2013 06:26, Andreas Pieber <anpieber@gmail.com> wrote:

>
>
> In general I still get a stall feeling in my stomage seeing all those
> enterprise features. Keeping them directly at Karaf sounds like a bad idea.
> We have already problems with the other enterprise features and their
> versions (e.g. Spring). Maybe it's slowly getting time to decide how we
> want to manage such external feature bundles? I add the dev list for CC to
> get this question explicitly to the dev community.
>
>

--f46d04426eda0df66e04d6af912a--