Mailing-List: contact dev-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <51683C57.2050403@nanthrax.net>
Date: Fri, 12 Apr 2013 18:54:47 +0200
From: =?ISO-8859-1?Q?Jean-Baptiste_Onofr=E9?= <jb@nanthrax.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: dev@karaf.apache.org
Subject: Re: features -> subsystems?
References: <5166B780.8030201@die-schneider.net>
 <5167B1D4.2030802@nanthrax.net> <5167B7F5.4010005@die-schneider.net>
 <5167B986.7050806@nanthrax.net> <51683AC7.1080203@gmail.com>
In-Reply-To: <51683AC7.1080203@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

Hi Andrei,

the first plan is to coexist.

It's the same plan for P2 repositories.

Features is the central and main provisioning for Karaf: we don't plan=20
to move to something else for now.
However, provide "bridges" between others systems (like subsystems and=20
P2) is interesting (both in the runtime and in the karaf-maven-plugin).

The scope coverage of the Karaf features is "larger" (at least for now)=20
than subsystem. For instance, the ConfigAdmin/ConfigFile support is very=20
limited in subsystems comparing to Karaf Features.

Regards
JB

On 04/12/2013 06:48 PM, Andrei Pozolotin wrote:
>      Jean-Baptiste
>
>      Can you please clarify what are karaf plans
>      as it relates to features vs subsystems?
>      http://blog.osgi.org/2012/06/core-release-5-and-enterprise-release=
-5.html
>      * will features be replaced by subsystems?
>      * will features continue as independent?
>      * will they co-exist
>      * etc.
>
>      Thank you,
>
>      Andrei
>
>

--=20
Jean-Baptiste Onofr=E9
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com