You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@karaf.apache.org by Achim Nierbeck <bc...@googlemail.com> on 2012/02/02 09:30:31 UTC
[PROPOSAL] A features-fragment for extending external Features
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
--
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Re: [PROPOSAL] A features-fragment for extending external Features
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
I got the same idea, but Achim explained it's different than a trigger.
A trigger means (or "embedded" features) require a new feature,
something like:
<feature name="karaf-war">
<feature>war</feature>
<bundle>war-commands</bundle>
</feature>
(same with trigger).
So it means that it's not transparent for the users, as they have to use
a specific karaf-war feature.
The Achim proposal is to install a new feature automatically when the
pax web war is installed, without modifying the "source" feature (pax
web war for instance).
Regards
JB
On 02/02/2012 11:10 AM, Ioannis Canellos wrote:
> +1 for the idea. I am not very fond of the naming (fragment / host) it looks more like a trigger rather than a fragment.
>
> Does it make any sense to support multiple hosts?
>
>
> On 2 Φεβ 2012, at 10:42 π.μ., Andreas Pieber wrote:
>
>> I really like the fragment idea. Actually I've encountered such situations
>> as you described already more than once :-/. But I think only extending
>> wont be enough; in addition it would be also required to remove/ignore
>> bundles from the host.
>>
>> Otherwise +1
>>
>> Kind regards,
>> Andreas
>>
>> On Thu, Feb 2, 2012 at 09:30, Achim Nierbeck<bc...@googlemail.com>wrote:
>>
>>> Hi all,
>>>
>>> when I tried to work on https://issues.apache.org/jira/browse/KARAF-1017last
>>> 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
>>>
>>> --
>>>
>>> Apache Karaf<http://karaf.apache.org/> Committer& PMC
>>> OPS4J Pax Web<http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer&
>>> Project Lead
>>> blog<http://notizblog.nierbeck.de/>
>>>
>
> Ioannis Canellos
> FuseSource
>
> Blog: http://iocanel.blogspot.com
> Apache Karaf Committer& PMC
> Apache Camel Committer
> Apache ServiceMix Committer
> Apache Gora Committer
> Apache DirectMemory Committer
>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [PROPOSAL] A features-fragment for extending external Features
Posted by Achim Nierbeck <bc...@googlemail.com>.
well I tried to differntiate from any post/pre scripting ideas which are
already around and I though
an analogy to the fragment-bundle and host would be best :)
Concerning the multiple Hosts I have no objections :)
2012/2/2 Ioannis Canellos <io...@gmail.com>
> +1 for the idea. I am not very fond of the naming (fragment / host) it
> looks more like a trigger rather than a fragment.
>
> Does it make any sense to support multiple hosts?
>
>
> On 2 Φεβ 2012, at 10:42 π.μ., Andreas Pieber wrote:
>
> > I really like the fragment idea. Actually I've encountered such
> situations
> > as you described already more than once :-/. But I think only extending
> > wont be enough; in addition it would be also required to remove/ignore
> > bundles from the host.
> >
> > Otherwise +1
> >
> > Kind regards,
> > Andreas
> >
> > On Thu, Feb 2, 2012 at 09:30, Achim Nierbeck <bcanhome@googlemail.com
> >wrote:
> >
> >> Hi all,
> >>
> >> when I tried to work on
> https://issues.apache.org/jira/browse/KARAF-1017last
> >> 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
> >>
> >> --
> >>
> >> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> >> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
> Committer &
> >> Project Lead
> >> blog <http://notizblog.nierbeck.de/>
> >>
>
> Ioannis Canellos
> FuseSource
>
> Blog: http://iocanel.blogspot.com
> Apache Karaf Committer & PMC
> Apache Camel Committer
> Apache ServiceMix Committer
> Apache Gora Committer
> Apache DirectMemory Committer
>
>
--
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Re: [PROPOSAL] A features-fragment for extending external Features
Posted by Ioannis Canellos <io...@gmail.com>.
+1 for the idea. I am not very fond of the naming (fragment / host) it looks more like a trigger rather than a fragment.
Does it make any sense to support multiple hosts?
On 2 Φεβ 2012, at 10:42 π.μ., Andreas Pieber wrote:
> I really like the fragment idea. Actually I've encountered such situations
> as you described already more than once :-/. But I think only extending
> wont be enough; in addition it would be also required to remove/ignore
> bundles from the host.
>
> Otherwise +1
>
> Kind regards,
> Andreas
>
> On Thu, Feb 2, 2012 at 09:30, Achim Nierbeck <bc...@googlemail.com>wrote:
>
>> Hi all,
>>
>> when I tried to work on https://issues.apache.org/jira/browse/KARAF-1017last
>> 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
>>
>> --
>>
>> Apache Karaf <http://karaf.apache.org/> Committer & PMC
>> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
>> Project Lead
>> blog <http://notizblog.nierbeck.de/>
>>
Ioannis Canellos
FuseSource
Blog: http://iocanel.blogspot.com
Apache Karaf Committer & PMC
Apache Camel Committer
Apache ServiceMix Committer
Apache Gora Committer
Apache DirectMemory Committer
Re: [PROPOSAL] A features-fragment for extending external Features
Posted by Andreas Pieber <an...@gmail.com>.
I don't think it's a big deal to use karaf feature web for 3.0 and pax-web
feature for 3.1. As long as there is no difference from a user point of
view I don't see any problems here.
Kind regards,
Andreas
2012/2/2 Jean-Baptiste Onofré <jb...@nanthrax.net>
> The problem is that it means that we won't be able to use the Pax Web
> features in Karaf 3.0, which is the opposite about what we discussed before.
>
> We can still use a "karaf feature" for web.
>
> Regards
> JB
>
>
> On 02/02/2012 11:11 AM, Łukasz Dywicki wrote:
>
>> +1 for doing that, -1 for pushing it into Karaf 3.0. As we discussed in
>> one from previous topics we should start stabilizing trunk to finally
>> prepare RC1. We lived so long without fragment features and I believe we
>> can release 3.0 without it too.
>>
>> Best regards,
>> Lukasz Dywicki
>> --
>> Code-House
>> http://code-house.org
>>
>> Wiadomość napisana przez Andreas Pieber w dniu 2 lut 2012, o godz. 09:42:
>>
>> I really like the fragment idea. Actually I've encountered such
>>> situations
>>> as you described already more than once :-/. But I think only extending
>>> wont be enough; in addition it would be also required to remove/ignore
>>> bundles from the host.
>>>
>>> Otherwise +1
>>>
>>> Kind regards,
>>> Andreas
>>>
>>> On Thu, Feb 2, 2012 at 09:30, Achim Nierbeck<bc...@googlemail.com>
>>> >wrote:
>>>
>>> Hi all,
>>>>
>>>> when I tried to work on https://issues.apache.org/**
>>>> jira/browse/KARAF-1017last<https://issues.apache.org/jira/browse/KARAF-1017last>
>>>> 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
>>>>
>>>> --
>>>>
>>>> Apache Karaf<http://karaf.apache.org/**> Committer& PMC
>>>>
>>>> OPS4J Pax Web<http://wiki.ops4j.org/**display/paxweb/Pax+Web/<http://wiki.ops4j.org/display/paxweb/Pax+Web/>>
>>>> Committer&
>>>> Project Lead
>>>> blog<http://notizblog.**nierbeck.de/ <http://notizblog.nierbeck.de/>>
>>>>
>>>>
>>
>>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: [PROPOSAL] A features-fragment for extending external Features
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
The problem is that it means that we won't be able to use the Pax Web
features in Karaf 3.0, which is the opposite about what we discussed before.
We can still use a "karaf feature" for web.
Regards
JB
On 02/02/2012 11:11 AM, Łukasz Dywicki wrote:
> +1 for doing that, -1 for pushing it into Karaf 3.0. As we discussed in one from previous topics we should start stabilizing trunk to finally prepare RC1. We lived so long without fragment features and I believe we can release 3.0 without it too.
>
> Best regards,
> Lukasz Dywicki
> --
> Code-House
> http://code-house.org
>
> Wiadomość napisana przez Andreas Pieber w dniu 2 lut 2012, o godz. 09:42:
>
>> I really like the fragment idea. Actually I've encountered such situations
>> as you described already more than once :-/. But I think only extending
>> wont be enough; in addition it would be also required to remove/ignore
>> bundles from the host.
>>
>> Otherwise +1
>>
>> Kind regards,
>> Andreas
>>
>> On Thu, Feb 2, 2012 at 09:30, Achim Nierbeck<bc...@googlemail.com>wrote:
>>
>>> Hi all,
>>>
>>> when I tried to work on https://issues.apache.org/jira/browse/KARAF-1017last
>>> 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
>>>
>>> --
>>>
>>> Apache Karaf<http://karaf.apache.org/> Committer& PMC
>>> OPS4J Pax Web<http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer&
>>> Project Lead
>>> blog<http://notizblog.nierbeck.de/>
>>>
>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [PROPOSAL] A features-fragment for extending external Features
Posted by Achim Nierbeck <bc...@googlemail.com>.
Well if we decide this to be not included in 3.0 we don't need to use the
pax-web features for karaf either.
regards, Achim
2012/2/2 Andreas Pieber <an...@gmail.com>
> +1 @3.1; I'm completely with Lukasz on this one
>
> @Ioannis trigger sounds also strange to me. Maybe "modifier"?; I don't
> think that this will make much sense. Such situations would be rather
> seldom (tbh I cant remember to encounter any of them till now) but maybe
> lead to missuse.
>
> Kind regards,
> Andreas
>
> 2012/2/2 Łukasz Dywicki <lu...@code-house.org>
>
> > +1 for doing that, -1 for pushing it into Karaf 3.0. As we discussed in
> > one from previous topics we should start stabilizing trunk to finally
> > prepare RC1. We lived so long without fragment features and I believe we
> > can release 3.0 without it too.
> >
> > Best regards,
> > Lukasz Dywicki
> > --
> > Code-House
> > http://code-house.org
> >
> > Wiadomość napisana przez Andreas Pieber w dniu 2 lut 2012, o godz. 09:42:
> >
> > > I really like the fragment idea. Actually I've encountered such
> > situations
> > > as you described already more than once :-/. But I think only extending
> > > wont be enough; in addition it would be also required to remove/ignore
> > > bundles from the host.
> > >
> > > Otherwise +1
> > >
> > > Kind regards,
> > > Andreas
> > >
> > > On Thu, Feb 2, 2012 at 09:30, Achim Nierbeck <bcanhome@googlemail.com
> > >wrote:
> > >
> > >> Hi all,
> > >>
> > >> when I tried to work on
> > https://issues.apache.org/jira/browse/KARAF-1017last
> > >> 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
> > >>
> > >> --
> > >>
> > >> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> > >> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
> > Committer &
> > >> Project Lead
> > >> blog <http://notizblog.nierbeck.de/>
> > >>
> >
> >
>
--
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Re: [PROPOSAL] A features-fragment for extending external Features
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Yes, we had a consensus in this way I guess ;)
Regards
JB
On 02/02/2012 11:44 AM, Achim Nierbeck wrote:
> So basically we postpone the features-fragmen and the inclusion of the
> pax-web feature for Pax web 2.0 to 3.1 of Karaf,
> did I get this right?
>
> regards, Achim
>
> 2012/2/2 Jean-Baptiste Onofré<jb...@nanthrax.net>
>
>> OK, so it means that this "fragment" feature could also be postponed to
>> 3.1.
>>
>> I'm ok with that.
>>
>> Anyway, I'm gonna cut the karaf-3.0.x branch soon (tonight or tomorrow
>> morning).
>>
>> Regards
>> JB
>>
>>
>> On 02/02/2012 11:22 AM, Andreas Pieber wrote:
>>
>>> +1 @3.1; I'm completely with Lukasz on this one
>>>
>>> @Ioannis trigger sounds also strange to me. Maybe "modifier"?; I don't
>>> think that this will make much sense. Such situations would be rather
>>> seldom (tbh I cant remember to encounter any of them till now) but maybe
>>> lead to missuse.
>>>
>>> Kind regards,
>>> Andreas
>>>
>>> 2012/2/2 Łukasz Dywicki<lu...@code-house.org>
>>>
>>> +1 for doing that, -1 for pushing it into Karaf 3.0. As we discussed in
>>>> one from previous topics we should start stabilizing trunk to finally
>>>> prepare RC1. We lived so long without fragment features and I believe we
>>>> can release 3.0 without it too.
>>>>
>>>> Best regards,
>>>> Lukasz Dywicki
>>>> --
>>>> Code-House
>>>> http://code-house.org
>>>>
>>>> Wiadomość napisana przez Andreas Pieber w dniu 2 lut 2012, o godz. 09:42:
>>>>
>>>> I really like the fragment idea. Actually I've encountered such
>>>>>
>>>> situations
>>>>
>>>>> as you described already more than once :-/. But I think only extending
>>>>> wont be enough; in addition it would be also required to remove/ignore
>>>>> bundles from the host.
>>>>>
>>>>> Otherwise +1
>>>>>
>>>>> Kind regards,
>>>>> Andreas
>>>>>
>>>>> On Thu, Feb 2, 2012 at 09:30, Achim Nierbeck<bc...@googlemail.com>
>>>>> wrote:
>>>>>
>>>>> Hi all,
>>>>>>
>>>>>> when I tried to work on
>>>>>>
>>>>> https://issues.apache.org/**jira/browse/KARAF-1017last<https://issues.apache.org/jira/browse/KARAF-1017last>
>>>>
>>>>> 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
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Apache Karaf<http://karaf.apache.org/**> Committer& PMC
>>>>>>
>>>>>> OPS4J Pax Web<http://wiki.ops4j.org/**display/paxweb/Pax+Web/<http://wiki.ops4j.org/display/paxweb/Pax+Web/>
>>>>>>>
>>>>>>
>>>>> Committer&
>>>>
>>>>> Project Lead
>>>>>> blog<http://notizblog.**nierbeck.de/<http://notizblog.nierbeck.de/>>
>>>>>>
>>>>>>
>>>>
>>>>
>>>
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>
>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [PROPOSAL] A features-fragment for extending external Features
Posted by Achim Nierbeck <bc...@googlemail.com>.
So basically we postpone the features-fragmen and the inclusion of the
pax-web feature for Pax web 2.0 to 3.1 of Karaf,
did I get this right?
regards, Achim
2012/2/2 Jean-Baptiste Onofré <jb...@nanthrax.net>
> OK, so it means that this "fragment" feature could also be postponed to
> 3.1.
>
> I'm ok with that.
>
> Anyway, I'm gonna cut the karaf-3.0.x branch soon (tonight or tomorrow
> morning).
>
> Regards
> JB
>
>
> On 02/02/2012 11:22 AM, Andreas Pieber wrote:
>
>> +1 @3.1; I'm completely with Lukasz on this one
>>
>> @Ioannis trigger sounds also strange to me. Maybe "modifier"?; I don't
>> think that this will make much sense. Such situations would be rather
>> seldom (tbh I cant remember to encounter any of them till now) but maybe
>> lead to missuse.
>>
>> Kind regards,
>> Andreas
>>
>> 2012/2/2 Łukasz Dywicki<lu...@code-house.org>
>>
>> +1 for doing that, -1 for pushing it into Karaf 3.0. As we discussed in
>>> one from previous topics we should start stabilizing trunk to finally
>>> prepare RC1. We lived so long without fragment features and I believe we
>>> can release 3.0 without it too.
>>>
>>> Best regards,
>>> Lukasz Dywicki
>>> --
>>> Code-House
>>> http://code-house.org
>>>
>>> Wiadomość napisana przez Andreas Pieber w dniu 2 lut 2012, o godz. 09:42:
>>>
>>> I really like the fragment idea. Actually I've encountered such
>>>>
>>> situations
>>>
>>>> as you described already more than once :-/. But I think only extending
>>>> wont be enough; in addition it would be also required to remove/ignore
>>>> bundles from the host.
>>>>
>>>> Otherwise +1
>>>>
>>>> Kind regards,
>>>> Andreas
>>>>
>>>> On Thu, Feb 2, 2012 at 09:30, Achim Nierbeck<bc...@googlemail.com>
>>>> wrote:
>>>>
>>>> Hi all,
>>>>>
>>>>> when I tried to work on
>>>>>
>>>> https://issues.apache.org/**jira/browse/KARAF-1017last<https://issues.apache.org/jira/browse/KARAF-1017last>
>>>
>>>> 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
>>>>>
>>>>> --
>>>>>
>>>>> Apache Karaf<http://karaf.apache.org/**> Committer& PMC
>>>>>
>>>>> OPS4J Pax Web<http://wiki.ops4j.org/**display/paxweb/Pax+Web/<http://wiki.ops4j.org/display/paxweb/Pax+Web/>
>>>>> >
>>>>>
>>>> Committer&
>>>
>>>> Project Lead
>>>>> blog<http://notizblog.**nierbeck.de/ <http://notizblog.nierbeck.de/>>
>>>>>
>>>>>
>>>
>>>
>>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
--
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Re: [PROPOSAL] A features-fragment for extending external Features
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
OK, so it means that this "fragment" feature could also be postponed to 3.1.
I'm ok with that.
Anyway, I'm gonna cut the karaf-3.0.x branch soon (tonight or tomorrow
morning).
Regards
JB
On 02/02/2012 11:22 AM, Andreas Pieber wrote:
> +1 @3.1; I'm completely with Lukasz on this one
>
> @Ioannis trigger sounds also strange to me. Maybe "modifier"?; I don't
> think that this will make much sense. Such situations would be rather
> seldom (tbh I cant remember to encounter any of them till now) but maybe
> lead to missuse.
>
> Kind regards,
> Andreas
>
> 2012/2/2 Łukasz Dywicki<lu...@code-house.org>
>
>> +1 for doing that, -1 for pushing it into Karaf 3.0. As we discussed in
>> one from previous topics we should start stabilizing trunk to finally
>> prepare RC1. We lived so long without fragment features and I believe we
>> can release 3.0 without it too.
>>
>> Best regards,
>> Lukasz Dywicki
>> --
>> Code-House
>> http://code-house.org
>>
>> Wiadomość napisana przez Andreas Pieber w dniu 2 lut 2012, o godz. 09:42:
>>
>>> I really like the fragment idea. Actually I've encountered such
>> situations
>>> as you described already more than once :-/. But I think only extending
>>> wont be enough; in addition it would be also required to remove/ignore
>>> bundles from the host.
>>>
>>> Otherwise +1
>>>
>>> Kind regards,
>>> Andreas
>>>
>>> On Thu, Feb 2, 2012 at 09:30, Achim Nierbeck<bcanhome@googlemail.com
>>> wrote:
>>>
>>>> Hi all,
>>>>
>>>> when I tried to work on
>> https://issues.apache.org/jira/browse/KARAF-1017last
>>>> 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
>>>>
>>>> --
>>>>
>>>> Apache Karaf<http://karaf.apache.org/> Committer& PMC
>>>> OPS4J Pax Web<http://wiki.ops4j.org/display/paxweb/Pax+Web/>
>> Committer&
>>>> Project Lead
>>>> blog<http://notizblog.nierbeck.de/>
>>>>
>>
>>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [PROPOSAL] A features-fragment for extending external Features
Posted by Andreas Pieber <an...@gmail.com>.
+1 @3.1; I'm completely with Lukasz on this one
@Ioannis trigger sounds also strange to me. Maybe "modifier"?; I don't
think that this will make much sense. Such situations would be rather
seldom (tbh I cant remember to encounter any of them till now) but maybe
lead to missuse.
Kind regards,
Andreas
2012/2/2 Łukasz Dywicki <lu...@code-house.org>
> +1 for doing that, -1 for pushing it into Karaf 3.0. As we discussed in
> one from previous topics we should start stabilizing trunk to finally
> prepare RC1. We lived so long without fragment features and I believe we
> can release 3.0 without it too.
>
> Best regards,
> Lukasz Dywicki
> --
> Code-House
> http://code-house.org
>
> Wiadomość napisana przez Andreas Pieber w dniu 2 lut 2012, o godz. 09:42:
>
> > I really like the fragment idea. Actually I've encountered such
> situations
> > as you described already more than once :-/. But I think only extending
> > wont be enough; in addition it would be also required to remove/ignore
> > bundles from the host.
> >
> > Otherwise +1
> >
> > Kind regards,
> > Andreas
> >
> > On Thu, Feb 2, 2012 at 09:30, Achim Nierbeck <bcanhome@googlemail.com
> >wrote:
> >
> >> Hi all,
> >>
> >> when I tried to work on
> https://issues.apache.org/jira/browse/KARAF-1017last
> >> 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
> >>
> >> --
> >>
> >> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> >> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
> Committer &
> >> Project Lead
> >> blog <http://notizblog.nierbeck.de/>
> >>
>
>
Re: [PROPOSAL] A features-fragment for extending external Features
Posted by Łukasz Dywicki <lu...@code-house.org>.
+1 for doing that, -1 for pushing it into Karaf 3.0. As we discussed in one from previous topics we should start stabilizing trunk to finally prepare RC1. We lived so long without fragment features and I believe we can release 3.0 without it too.
Best regards,
Lukasz Dywicki
--
Code-House
http://code-house.org
Wiadomość napisana przez Andreas Pieber w dniu 2 lut 2012, o godz. 09:42:
> I really like the fragment idea. Actually I've encountered such situations
> as you described already more than once :-/. But I think only extending
> wont be enough; in addition it would be also required to remove/ignore
> bundles from the host.
>
> Otherwise +1
>
> Kind regards,
> Andreas
>
> On Thu, Feb 2, 2012 at 09:30, Achim Nierbeck <bc...@googlemail.com>wrote:
>
>> Hi all,
>>
>> when I tried to work on https://issues.apache.org/jira/browse/KARAF-1017last
>> 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
>>
>> --
>>
>> Apache Karaf <http://karaf.apache.org/> Committer & PMC
>> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
>> Project Lead
>> blog <http://notizblog.nierbeck.de/>
>>
Re: [PROPOSAL] A features-fragment for extending external Features
Posted by Andreas Pieber <an...@gmail.com>.
I really like the fragment idea. Actually I've encountered such situations
as you described already more than once :-/. But I think only extending
wont be enough; in addition it would be also required to remove/ignore
bundles from the host.
Otherwise +1
Kind regards,
Andreas
On Thu, Feb 2, 2012 at 09:30, Achim Nierbeck <bc...@googlemail.com>wrote:
> Hi all,
>
> when I tried to work on https://issues.apache.org/jira/browse/KARAF-1017last
> 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
>
> --
>
> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
> Project Lead
> blog <http://notizblog.nierbeck.de/>
>
Re: [PROPOSAL] A features-fragment for extending external Features
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
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