You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@karaf.apache.org by Jean-Baptiste Onofré <jb...@nanthrax.net> on 2018/11/23 04:16:06 UTC
[DISCUSS] Apache Karaf 4.3.x and resource repositories
Hi guys,
as discussed since some weeks, Karaf 4.2.2 should be in vote in couple
of weeks.
I started a Karaf 4.3.x branch locally and master will become 4.3.x once
4.2.x branch will be created.
Karaf 4.3.x will update to OSGi R7 and other major dependency updates. I
will include a new feature/improvement in 4.3.x:
https://issues.apache.org/jira/browse/KARAF-6000
Today, Karaf supports resources repositories (yaml or xml) in
etc/org.apache.karaf.features.cfg. A resource repository looks a bit
like "old" OBR: it contains resources (bundles but also config, etc)
with associated requirements and capabilities.
The resolver uses those requirements and capabilities to find the
dependency resources he should install when installing a feature or a
bundle. That's convenient and close to the "core" OSGi approach.
However, the resource repositories set defined in
etc/org.apache.karaf.features.cfg is static: it's loaded and evaluated
when the features service starts, then the resolver uses it.
The proposal in KARAF-6000 is to be able to update the resource
repositories set on the fly (with dedicated commands for instance) and,
each time the resource repositories set is modified, perform a new whole
resolution.
Basically, it means that only the "standard" Karaf features would be
required at startup, the users will be able to use only resource
repositories (not features repositories) once Karaf is started.
I already started a PoC for KARAF-6000.
Thoughts ?
Regards
JB
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [DISCUSS] Apache Karaf 4.3.x and resource repositories
Posted by Freeman Fang <fr...@gmail.com>.
Agree, since feature is really essential for Karaf and I believe most Karaf users build their projects based on it.
So we should keep current feature behaviour as is and we can introduce new resource repository behaviour from configuration switch.
Thanks!
－－－－－－－－－－－－－
Freeman(Yue) Fang
Red Hat, Inc.
> On Nov 23, 2018, at 3:34 PM, Francois Papon <fr...@openobject.fr> wrote:
>
> Hi,
>
> Yes I also agree with this, I think we should keep the Karaf features as
> a default usage for end-users ;)
>
> regards,
>
> François Papon
> fpapon@apache.org
>
> Le 23/11/2018 à 11:11, Jean-Baptiste Onofré a écrit :
>> Fully agree. Don't get me wrong: I don't want to remove features. We have lot of unique features in Karaf features that can't achieved using resources repositories.
>>
>> The idea is more to give a more dynamic and generic approach to OSGi users as transition to use Karaf features.
>>
>> Regards
>> JB
>>
>> Le 23 nov. 2018 à 07:53, à 07:53, Grzegorz Grzybek <gr...@gmail.com> a écrit:
>>> Hello
>>>
>>> Nice round KARAF-6000 number!
>>>
>>> I added a comment under KARAF-6000 - I generally think that going the
>>> _OSGi
>>> way_ is a good thing™, but we have to remember about all the features
>>> of
>>> ... Karaf features - blacklisting, prerequisites, overrides (bundle and
>>> feature overrides) which may not be directly translatable to OSGi R7
>>> repositories.
>>> But it's a great subject to investigate and I'll be more than happy to
>>> review your PoC!
>>>
>>> best regards
>>> Grzegorz Grzybek
>>>
>>> pt., 23 lis 2018 o 05:16 Jean-Baptiste Onofré <jb...@nanthrax.net>
>>> napisał(a):
>>>
>>>> Hi guys,
>>>>
>>>> as discussed since some weeks, Karaf 4.2.2 should be in vote in
>>> couple
>>>> of weeks.
>>>> I started a Karaf 4.3.x branch locally and master will become 4.3.x
>>> once
>>>> 4.2.x branch will be created.
>>>>
>>>> Karaf 4.3.x will update to OSGi R7 and other major dependency
>>> updates. I
>>>> will include a new feature/improvement in 4.3.x:
>>>>
>>>> https://issues.apache.org/jira/browse/KARAF-6000
>>>>
>>>> Today, Karaf supports resources repositories (yaml or xml) in
>>>> etc/org.apache.karaf.features.cfg. A resource repository looks a bit
>>>> like "old" OBR: it contains resources (bundles but also config, etc)
>>>> with associated requirements and capabilities.
>>>> The resolver uses those requirements and capabilities to find the
>>>> dependency resources he should install when installing a feature or a
>>>> bundle. That's convenient and close to the "core" OSGi approach.
>>>>
>>>> However, the resource repositories set defined in
>>>> etc/org.apache.karaf.features.cfg is static: it's loaded and
>>> evaluated
>>>> when the features service starts, then the resolver uses it.
>>>>
>>>> The proposal in KARAF-6000 is to be able to update the resource
>>>> repositories set on the fly (with dedicated commands for instance)
>>> and,
>>>> each time the resource repositories set is modified, perform a new
>>> whole
>>>> resolution.
>>>> Basically, it means that only the "standard" Karaf features would be
>>>> required at startup, the users will be able to use only resource
>>>> repositories (not features repositories) once Karaf is started.
>>>> I already started a PoC for KARAF-6000.
>>>>
>>>> Thoughts ?
>>>>
>>>> Regards
>>>> JB
>>>> --
>>>> Jean-Baptiste Onofré
>>>> jbonofre@apache.org
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com
>>>>
>
Re: [DISCUSS] Apache Karaf 4.3.x and resource repositories
Posted by Francois Papon <fr...@openobject.fr>.
Hi,
Yes I also agree with this, I think we should keep the Karaf features as
a default usage for end-users ;)
regards,
François Papon
fpapon@apache.org
Le 23/11/2018 à 11:11, Jean-Baptiste Onofré a écrit :
> Fully agree. Don't get me wrong: I don't want to remove features. We have lot of unique features in Karaf features that can't achieved using resources repositories.
>
> The idea is more to give a more dynamic and generic approach to OSGi users as transition to use Karaf features.
>
> Regards
> JB
>
> Le 23 nov. 2018 à 07:53, à 07:53, Grzegorz Grzybek <gr...@gmail.com> a écrit:
>> Hello
>>
>> Nice round KARAF-6000 number!
>>
>> I added a comment under KARAF-6000 - I generally think that going the
>> _OSGi
>> way_ is a good thing™, but we have to remember about all the features
>> of
>> ... Karaf features - blacklisting, prerequisites, overrides (bundle and
>> feature overrides) which may not be directly translatable to OSGi R7
>> repositories.
>> But it's a great subject to investigate and I'll be more than happy to
>> review your PoC!
>>
>> best regards
>> Grzegorz Grzybek
>>
>> pt., 23 lis 2018 o 05:16 Jean-Baptiste Onofré <jb...@nanthrax.net>
>> napisał(a):
>>
>>> Hi guys,
>>>
>>> as discussed since some weeks, Karaf 4.2.2 should be in vote in
>> couple
>>> of weeks.
>>> I started a Karaf 4.3.x branch locally and master will become 4.3.x
>> once
>>> 4.2.x branch will be created.
>>>
>>> Karaf 4.3.x will update to OSGi R7 and other major dependency
>> updates. I
>>> will include a new feature/improvement in 4.3.x:
>>>
>>> https://issues.apache.org/jira/browse/KARAF-6000
>>>
>>> Today, Karaf supports resources repositories (yaml or xml) in
>>> etc/org.apache.karaf.features.cfg. A resource repository looks a bit
>>> like "old" OBR: it contains resources (bundles but also config, etc)
>>> with associated requirements and capabilities.
>>> The resolver uses those requirements and capabilities to find the
>>> dependency resources he should install when installing a feature or a
>>> bundle. That's convenient and close to the "core" OSGi approach.
>>>
>>> However, the resource repositories set defined in
>>> etc/org.apache.karaf.features.cfg is static: it's loaded and
>> evaluated
>>> when the features service starts, then the resolver uses it.
>>>
>>> The proposal in KARAF-6000 is to be able to update the resource
>>> repositories set on the fly (with dedicated commands for instance)
>> and,
>>> each time the resource repositories set is modified, perform a new
>> whole
>>> resolution.
>>> Basically, it means that only the "standard" Karaf features would be
>>> required at startup, the users will be able to use only resource
>>> repositories (not features repositories) once Karaf is started.
>>> I already started a PoC for KARAF-6000.
>>>
>>> Thoughts ?
>>>
>>> Regards
>>> JB
>>> --
>>> Jean-Baptiste Onofré
>>> jbonofre@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
Re: [DISCUSS] Apache Karaf 4.3.x and resource repositories
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Fully agree. Don't get me wrong: I don't want to remove features. We have lot of unique features in Karaf features that can't achieved using resources repositories.
The idea is more to give a more dynamic and generic approach to OSGi users as transition to use Karaf features.
Regards
JB
Le 23 nov. 2018 à 07:53, à 07:53, Grzegorz Grzybek <gr...@gmail.com> a écrit:
>Hello
>
>Nice round KARAF-6000 number!
>
>I added a comment under KARAF-6000 - I generally think that going the
>_OSGi
>way_ is a good thing™, but we have to remember about all the features
>of
>... Karaf features - blacklisting, prerequisites, overrides (bundle and
>feature overrides) which may not be directly translatable to OSGi R7
>repositories.
>But it's a great subject to investigate and I'll be more than happy to
>review your PoC!
>
>best regards
>Grzegorz Grzybek
>
>pt., 23 lis 2018 o 05:16 Jean-Baptiste Onofré <jb...@nanthrax.net>
>napisał(a):
>
>> Hi guys,
>>
>> as discussed since some weeks, Karaf 4.2.2 should be in vote in
>couple
>> of weeks.
>> I started a Karaf 4.3.x branch locally and master will become 4.3.x
>once
>> 4.2.x branch will be created.
>>
>> Karaf 4.3.x will update to OSGi R7 and other major dependency
>updates. I
>> will include a new feature/improvement in 4.3.x:
>>
>> https://issues.apache.org/jira/browse/KARAF-6000
>>
>> Today, Karaf supports resources repositories (yaml or xml) in
>> etc/org.apache.karaf.features.cfg. A resource repository looks a bit
>> like "old" OBR: it contains resources (bundles but also config, etc)
>> with associated requirements and capabilities.
>> The resolver uses those requirements and capabilities to find the
>> dependency resources he should install when installing a feature or a
>> bundle. That's convenient and close to the "core" OSGi approach.
>>
>> However, the resource repositories set defined in
>> etc/org.apache.karaf.features.cfg is static: it's loaded and
>evaluated
>> when the features service starts, then the resolver uses it.
>>
>> The proposal in KARAF-6000 is to be able to update the resource
>> repositories set on the fly (with dedicated commands for instance)
>and,
>> each time the resource repositories set is modified, perform a new
>whole
>> resolution.
>> Basically, it means that only the "standard" Karaf features would be
>> required at startup, the users will be able to use only resource
>> repositories (not features repositories) once Karaf is started.
>> I already started a PoC for KARAF-6000.
>>
>> Thoughts ?
>>
>> Regards
>> JB
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
Re: [DISCUSS] Apache Karaf 4.3.x and resource repositories
Posted by Grzegorz Grzybek <gr...@gmail.com>.
Hello
Nice round KARAF-6000 number!
I added a comment under KARAF-6000 - I generally think that going the _OSGi
way_ is a good thing™, but we have to remember about all the features of
... Karaf features - blacklisting, prerequisites, overrides (bundle and
feature overrides) which may not be directly translatable to OSGi R7
repositories.
But it's a great subject to investigate and I'll be more than happy to
review your PoC!
best regards
Grzegorz Grzybek
pt., 23 lis 2018 o 05:16 Jean-Baptiste Onofré <jb...@nanthrax.net> napisał(a):
> Hi guys,
>
> as discussed since some weeks, Karaf 4.2.2 should be in vote in couple
> of weeks.
> I started a Karaf 4.3.x branch locally and master will become 4.3.x once
> 4.2.x branch will be created.
>
> Karaf 4.3.x will update to OSGi R7 and other major dependency updates. I
> will include a new feature/improvement in 4.3.x:
>
> https://issues.apache.org/jira/browse/KARAF-6000
>
> Today, Karaf supports resources repositories (yaml or xml) in
> etc/org.apache.karaf.features.cfg. A resource repository looks a bit
> like "old" OBR: it contains resources (bundles but also config, etc)
> with associated requirements and capabilities.
> The resolver uses those requirements and capabilities to find the
> dependency resources he should install when installing a feature or a
> bundle. That's convenient and close to the "core" OSGi approach.
>
> However, the resource repositories set defined in
> etc/org.apache.karaf.features.cfg is static: it's loaded and evaluated
> when the features service starts, then the resolver uses it.
>
> The proposal in KARAF-6000 is to be able to update the resource
> repositories set on the fly (with dedicated commands for instance) and,
> each time the resource repositories set is modified, perform a new whole
> resolution.
> Basically, it means that only the "standard" Karaf features would be
> required at startup, the users will be able to use only resource
> repositories (not features repositories) once Karaf is started.
> I already started a PoC for KARAF-6000.
>
> Thoughts ?
>
> Regards
> JB
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: [DISCUSS] Apache Karaf 4.3.x and resource repositories
Posted by Christian Schneider <ch...@die-schneider.net>.
That might even be similar to what I have in mind. Can you elaborate a bit
how it would work?
Christian
Am Fr., 23. Nov. 2018 um 11:35 Uhr schrieb Jean-Baptiste Onofré <
jb@nanthrax.net>:
> It's not a new concept. It's just better leverage bundle repositories in
> feature and have light features.
>
> Regards
> JB
>
> Le 23 nov. 2018 à 10:45, à 10:45, Christian Schneider <
> chris@die-schneider.net> a écrit:
> >I do not really understand what this approach does different to
> >features.
> >Can you elaborate a bit more?
> >
> >I think it would be great to go more into the direction of repositories
> >and
> >features that do not have to list all bundles but only the required
> >bundles
> >to let the resolver find the rest.
> >As far as I understand this does not require a completely new concept.
> >It
> >can be done based on the current features.
> >
> >Christian
> >
> >Am Fr., 23. Nov. 2018 um 05:16 Uhr schrieb Jean-Baptiste Onofré <
> >jb@nanthrax.net>:
> >
> >> Hi guys,
> >>
> >> as discussed since some weeks, Karaf 4.2.2 should be in vote in
> >couple
> >> of weeks.
> >> I started a Karaf 4.3.x branch locally and master will become 4.3.x
> >once
> >> 4.2.x branch will be created.
> >>
> >> Karaf 4.3.x will update to OSGi R7 and other major dependency
> >updates. I
> >> will include a new feature/improvement in 4.3.x:
> >>
> >> https://issues.apache.org/jira/browse/KARAF-6000
> >>
> >> Today, Karaf supports resources repositories (yaml or xml) in
> >> etc/org.apache.karaf.features.cfg. A resource repository looks a bit
> >> like "old" OBR: it contains resources (bundles but also config, etc)
> >> with associated requirements and capabilities.
> >> The resolver uses those requirements and capabilities to find the
> >> dependency resources he should install when installing a feature or a
> >> bundle. That's convenient and close to the "core" OSGi approach.
> >>
> >> However, the resource repositories set defined in
> >> etc/org.apache.karaf.features.cfg is static: it's loaded and
> >evaluated
> >> when the features service starts, then the resolver uses it.
> >>
> >> The proposal in KARAF-6000 is to be able to update the resource
> >> repositories set on the fly (with dedicated commands for instance)
> >and,
> >> each time the resource repositories set is modified, perform a new
> >whole
> >> resolution.
> >> Basically, it means that only the "standard" Karaf features would be
> >> required at startup, the users will be able to use only resource
> >> repositories (not features repositories) once Karaf is started.
> >> I already started a PoC for KARAF-6000.
> >>
> >> Thoughts ?
> >>
> >> Regards
> >> JB
> >> --
> >> Jean-Baptiste Onofré
> >> jbonofre@apache.org
> >> http://blog.nanthrax.net
> >> Talend - http://www.talend.com
> >>
> >
> >
> >--
> >--
> >Christian Schneider
> >http://www.liquid-reality.de
> >
> >Computer Scientist
> >http://www.adobe.com
>
--
--
Christian Schneider
http://www.liquid-reality.de
Computer Scientist
http://www.adobe.com
Re: [DISCUSS] Apache Karaf 4.3.x and resource repositories
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
It's not a new concept. It's just better leverage bundle repositories in feature and have light features.
Regards
JB
Le 23 nov. 2018 à 10:45, à 10:45, Christian Schneider <ch...@die-schneider.net> a écrit:
>I do not really understand what this approach does different to
>features.
>Can you elaborate a bit more?
>
>I think it would be great to go more into the direction of repositories
>and
>features that do not have to list all bundles but only the required
>bundles
>to let the resolver find the rest.
>As far as I understand this does not require a completely new concept.
>It
>can be done based on the current features.
>
>Christian
>
>Am Fr., 23. Nov. 2018 um 05:16 Uhr schrieb Jean-Baptiste Onofré <
>jb@nanthrax.net>:
>
>> Hi guys,
>>
>> as discussed since some weeks, Karaf 4.2.2 should be in vote in
>couple
>> of weeks.
>> I started a Karaf 4.3.x branch locally and master will become 4.3.x
>once
>> 4.2.x branch will be created.
>>
>> Karaf 4.3.x will update to OSGi R7 and other major dependency
>updates. I
>> will include a new feature/improvement in 4.3.x:
>>
>> https://issues.apache.org/jira/browse/KARAF-6000
>>
>> Today, Karaf supports resources repositories (yaml or xml) in
>> etc/org.apache.karaf.features.cfg. A resource repository looks a bit
>> like "old" OBR: it contains resources (bundles but also config, etc)
>> with associated requirements and capabilities.
>> The resolver uses those requirements and capabilities to find the
>> dependency resources he should install when installing a feature or a
>> bundle. That's convenient and close to the "core" OSGi approach.
>>
>> However, the resource repositories set defined in
>> etc/org.apache.karaf.features.cfg is static: it's loaded and
>evaluated
>> when the features service starts, then the resolver uses it.
>>
>> The proposal in KARAF-6000 is to be able to update the resource
>> repositories set on the fly (with dedicated commands for instance)
>and,
>> each time the resource repositories set is modified, perform a new
>whole
>> resolution.
>> Basically, it means that only the "standard" Karaf features would be
>> required at startup, the users will be able to use only resource
>> repositories (not features repositories) once Karaf is started.
>> I already started a PoC for KARAF-6000.
>>
>> Thoughts ?
>>
>> Regards
>> JB
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>
>
>--
>--
>Christian Schneider
>http://www.liquid-reality.de
>
>Computer Scientist
>http://www.adobe.com
Re: [DISCUSS] Apache Karaf 4.3.x and resource repositories
Posted by Christian Schneider <ch...@die-schneider.net>.
I do not really understand what this approach does different to features.
Can you elaborate a bit more?
I think it would be great to go more into the direction of repositories and
features that do not have to list all bundles but only the required bundles
to let the resolver find the rest.
As far as I understand this does not require a completely new concept. It
can be done based on the current features.
Christian
Am Fr., 23. Nov. 2018 um 05:16 Uhr schrieb Jean-Baptiste Onofré <
jb@nanthrax.net>:
> Hi guys,
>
> as discussed since some weeks, Karaf 4.2.2 should be in vote in couple
> of weeks.
> I started a Karaf 4.3.x branch locally and master will become 4.3.x once
> 4.2.x branch will be created.
>
> Karaf 4.3.x will update to OSGi R7 and other major dependency updates. I
> will include a new feature/improvement in 4.3.x:
>
> https://issues.apache.org/jira/browse/KARAF-6000
>
> Today, Karaf supports resources repositories (yaml or xml) in
> etc/org.apache.karaf.features.cfg. A resource repository looks a bit
> like "old" OBR: it contains resources (bundles but also config, etc)
> with associated requirements and capabilities.
> The resolver uses those requirements and capabilities to find the
> dependency resources he should install when installing a feature or a
> bundle. That's convenient and close to the "core" OSGi approach.
>
> However, the resource repositories set defined in
> etc/org.apache.karaf.features.cfg is static: it's loaded and evaluated
> when the features service starts, then the resolver uses it.
>
> The proposal in KARAF-6000 is to be able to update the resource
> repositories set on the fly (with dedicated commands for instance) and,
> each time the resource repositories set is modified, perform a new whole
> resolution.
> Basically, it means that only the "standard" Karaf features would be
> required at startup, the users will be able to use only resource
> repositories (not features repositories) once Karaf is started.
> I already started a PoC for KARAF-6000.
>
> Thoughts ?
>
> Regards
> JB
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
--
--
Christian Schneider
http://www.liquid-reality.de
Computer Scientist
http://www.adobe.com