karaf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré ...@nanthrax.net>
Subject Re: [PROPOSAL] A features-fragment for extending external Features
Date Thu, 02 Feb 2012 08:41:17 GMT
Hi Achim,

as discussed this morning on IRC, I'm +1 on that.

Especially, I think it should be included in Karaf 3.0.0 as it's more or 
less a requirement to use Pax Web features as we decided in Karaf 3.0.0.

Regards
JB

On 02/02/2012 09:30 AM, Achim Nierbeck wrote:
> Hi all,
>
> when I tried to work on  https://issues.apache.org/jira/browse/KARAF-1017 last
> night I noticed that
> our features are missing a nice "feature".
> Following situation right now.
>
> The Karaf standard feature does contain the http, war, http-whiteboard and
> jetty feature.
> Those features do not only contain the pax-web and jetty bundles but also
> some extra
> benefits of Karaf, the http and web commands.
>
> AFAIR we decided once that it would be best that every project does take
> care of the their features,
> as Camel and CXF (AFAIK) have done so far.
> For the pax-web project I did this for pax-web 2.0 which includes those
> features named above.
> The thing that is missing in the pax-web-features file are the http and web
> commands.
>
> *My proposal: *
> Introduce a new features element called *features-fragment*
> The tag could look like the following:
>
> <features-fragment name="http-command" host="http">
>       <bundle ....>
> </features-fragment>
>
> this fragment is supposed to be extending the hosting feature to add
> additional bundles which
> are also installed by the features service when the hosting feature is
> installed. The features service
> could look for all features-fragments that are "bound" to the host
> features.
>
> I think just creating a feature that depends on the http features like the
> following
>
> <feature name="http-command">
>       <feature>http</feature>
>       <bundle ....>
> </feature>
>
> is not enough and is actually also a regression of Karaf 3.0 vs. Karaf 2.2.x
>
> *Benefits: *
> This way we are able to easily adapt/extend external features with
> specialties needed in certain environments.
> Right now it would be that the external pax-web feature is extended with
> special Karaf commands.
> But I could also think this to be a nice enhancement for customers
> extending Karaf with their own features.
>
> Regards, Achim
>

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

Mime
View raw message