You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Guillaume Nodet <gn...@apache.org> on 2016/09/23 08:21:54 UTC
[DISCUSS] Upgrade Camel to Karaf 4
I'd like to start a discussion around upgrading Camel karaf support to
Karaf 4.
Karaf 4 has brought a number of changes that could be leveraged :
* no strong dependency on blueprint
* complete feature validation at build time
* more fine grained feature so that all dependencies can be expressed
I'd like to leverage those for Camel. This can be achieved either by
dropping support for Karaf 2 and 3, or by keeping both (effectively
duplicating the integration code in platforms/karaf to platforms/karaf4).
Also, it would make sense to upgrade to cxf 3.2-SNAPSHOT which I'm also
upgrading to Karaf 4.
Thoughts ?
Guillaume Nodet
Re: [DISCUSS] Upgrade Camel to Karaf 4
Posted by Claus Ibsen <cl...@gmail.com>.
We only support Karaf 4.x or newer.
So your PR is good and we would like to merge it.
On Tue, Oct 11, 2016 at 4:07 PM, Tomohisa Igarashi
<tm...@gmail.com> wrote:
> Hi,
>
> I just submitted a pull request for CAMEL-10124, migrating camel commands to
> karaf4 style. And found this thread is somehow related...
> https://issues.apache.org/jira/browse/CAMEL-10124
> https://github.com/apache/camel/pull/1206
>
> As far as I tested locally, current camel commands are working fine on
> karaf4 as well, although it's using deprecated API. The changeset I
> submitted migrates those to karaf4 style to remove deprecated API usage, but
> it doesn't work on karaf 2 and 3. So I'm wondering which versions of karaf
> should be supported by current camel upstream?
>
> Thanks,
> Tomo
>
>
> On 09/23/2016 05:21 PM, Guillaume Nodet wrote:
>>
>> I'd like to start a discussion around upgrading Camel karaf support to
>> Karaf 4.
>> Karaf 4 has brought a number of changes that could be leveraged :
>> * no strong dependency on blueprint
>> * complete feature validation at build time
>> * more fine grained feature so that all dependencies can be expressed
>>
>> I'd like to leverage those for Camel. This can be achieved either by
>> dropping support for Karaf 2 and 3, or by keeping both (effectively
>> duplicating the integration code in platforms/karaf to platforms/karaf4).
>>
>> Also, it would make sense to upgrade to cxf 3.2-SNAPSHOT which I'm also
>> upgrading to Karaf 4.
>>
>> Thoughts ?
>> Guillaume Nodet
>>
>
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: [DISCUSS] Upgrade Camel to Karaf 4
Posted by Tomohisa Igarashi <tm...@gmail.com>.
Hi,
I just submitted a pull request for CAMEL-10124, migrating camel commands to karaf4 style. And found this thread is somehow related...
https://issues.apache.org/jira/browse/CAMEL-10124
https://github.com/apache/camel/pull/1206
As far as I tested locally, current camel commands are working fine on karaf4 as well, although it's using deprecated API. The changeset I submitted migrates those to karaf4 style to remove deprecated API usage, but it doesn't work on karaf 2 and 3. So I'm wondering which versions of karaf should be supported by current camel upstream?
Thanks,
Tomo
On 09/23/2016 05:21 PM, Guillaume Nodet wrote:
> I'd like to start a discussion around upgrading Camel karaf support to
> Karaf 4.
> Karaf 4 has brought a number of changes that could be leveraged :
> * no strong dependency on blueprint
> * complete feature validation at build time
> * more fine grained feature so that all dependencies can be expressed
>
> I'd like to leverage those for Camel. This can be achieved either by
> dropping support for Karaf 2 and 3, or by keeping both (effectively
> duplicating the integration code in platforms/karaf to platforms/karaf4).
>
> Also, it would make sense to upgrade to cxf 3.2-SNAPSHOT which I'm also
> upgrading to Karaf 4.
>
> Thoughts ?
> Guillaume Nodet
>
Re: [DISCUSS] Upgrade Camel to Karaf 4
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
+1
Regards
JB
On Sep 23, 2016, 07:15, at 07:15, Daniel Kulp <dk...@apache.org> wrote:
>
>I think it\u2019s too late to do this for 2.18 (trying to get that out
>soon). Might make sense for 2.19.
>
>Dan
>
>
>> On Sep 23, 2016, at 4:21 AM, Guillaume Nodet <gn...@apache.org>
>wrote:
>>
>> I'd like to start a discussion around upgrading Camel karaf support
>to
>> Karaf 4.
>> Karaf 4 has brought a number of changes that could be leveraged :
>> * no strong dependency on blueprint
>> * complete feature validation at build time
>> * more fine grained feature so that all dependencies can be
>expressed
>>
>> I'd like to leverage those for Camel. This can be achieved either by
>> dropping support for Karaf 2 and 3, or by keeping both (effectively
>> duplicating the integration code in platforms/karaf to
>platforms/karaf4).
>>
>> Also, it would make sense to upgrade to cxf 3.2-SNAPSHOT which I'm
>also
>> upgrading to Karaf 4.
>>
>> Thoughts ?
>> Guillaume Nodet
>
>--
>Daniel Kulp
>dkulp@apache.org <ma...@apache.org> - http://dankulp.com/blog
><http://dankulp.com/blog>
>Talend Community Coder - http://coders.talend.com
><http://coders.talend.com/>
Re: [DISCUSS] Upgrade Camel to Karaf 4
Posted by Claus Ibsen <cl...@gmail.com>.
+1
On Fri, Sep 23, 2016 at 4:17 PM, Andrea Cosentino
<an...@yahoo.com.invalid> wrote:
> I agree with Daniel.
>
> Anyway this is something we can surely work on for the next release.
> --
> Andrea Cosentino
> ----------------------------------
> Apache Camel PMC Member
> Apache Karaf Committer
> Apache Servicemix Committer
> Email: ancosen1985@yahoo.com
> Twitter: @oscerd2
> Github: oscerd
>
>
>
> On Friday, September 23, 2016 4:15 PM, Daniel Kulp <dk...@apache.org> wrote:
>
> I think it’s too late to do this for 2.18 (trying to get that out soon). Might make sense for 2.19.
>
> Dan
>
>
>
>> On Sep 23, 2016, at 4:21 AM, Guillaume Nodet <gn...@apache.org> wrote:
>>
>> I'd like to start a discussion around upgrading Camel karaf support to
>> Karaf 4.
>> Karaf 4 has brought a number of changes that could be leveraged :
>> * no strong dependency on blueprint
>> * complete feature validation at build time
>> * more fine grained feature so that all dependencies can be expressed
>>
>> I'd like to leverage those for Camel. This can be achieved either by
>> dropping support for Karaf 2 and 3, or by keeping both (effectively
>> duplicating the integration code in platforms/karaf to platforms/karaf4).
>>
>> Also, it would make sense to upgrade to cxf 3.2-SNAPSHOT which I'm also
>> upgrading to Karaf 4.
>>
>> Thoughts ?
>> Guillaume Nodet
>
> --
> Daniel Kulp
> dkulp@apache.org <ma...@apache.org> - http://dankulp.com/blog <http://dankulp.com/blog>
> Talend Community Coder - http://coders.talend.com <http://coders.talend.com/
>>
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: [DISCUSS] Upgrade Camel to Karaf 4
Posted by Jon Anstey <ja...@gmail.com>.
+1
On Fri, Sep 23, 2016 at 11:47 AM, Andrea Cosentino <
ancosen1985@yahoo.com.invalid> wrote:
> I agree with Daniel.
>
> Anyway this is something we can surely work on for the next release.
> --
> Andrea Cosentino
> ----------------------------------
> Apache Camel PMC Member
> Apache Karaf Committer
> Apache Servicemix Committer
> Email: ancosen1985@yahoo.com
> Twitter: @oscerd2
> Github: oscerd
>
>
>
> On Friday, September 23, 2016 4:15 PM, Daniel Kulp <dk...@apache.org>
> wrote:
>
> I think it’s too late to do this for 2.18 (trying to get that out soon).
> Might make sense for 2.19.
>
> Dan
>
>
>
> > On Sep 23, 2016, at 4:21 AM, Guillaume Nodet <gn...@apache.org> wrote:
> >
> > I'd like to start a discussion around upgrading Camel karaf support to
> > Karaf 4.
> > Karaf 4 has brought a number of changes that could be leveraged :
> > * no strong dependency on blueprint
> > * complete feature validation at build time
> > * more fine grained feature so that all dependencies can be expressed
> >
> > I'd like to leverage those for Camel. This can be achieved either by
> > dropping support for Karaf 2 and 3, or by keeping both (effectively
> > duplicating the integration code in platforms/karaf to platforms/karaf4).
> >
> > Also, it would make sense to upgrade to cxf 3.2-SNAPSHOT which I'm also
> > upgrading to Karaf 4.
> >
> > Thoughts ?
> > Guillaume Nodet
>
> --
> Daniel Kulp
> dkulp@apache.org <ma...@apache.org> - http://dankulp.com/blog <
> http://dankulp.com/blog>
> Talend Community Coder - http://coders.talend.com <
> http://coders.talend.com/
> >
>
--
Cheers,
Jon
---------------
Red Hat, Inc.
Email: janstey@redhat.com
Web: http://redhat.com
Twitter: jon_anstey
Blog: http://janstey.blogspot.com
Camel in Action:
https://www.manning.com/books/camel-in-action-second-edition
Re: [DISCUSS] Upgrade Camel to Karaf 4
Posted by Luca Burgazzoli <lb...@gmail.com>.
+1
---
Luca Burgazzoli
On Fri, Sep 23, 2016 at 4:17 PM, Andrea Cosentino
<an...@yahoo.com.invalid> wrote:
> I agree with Daniel.
>
> Anyway this is something we can surely work on for the next release.
> --
> Andrea Cosentino
> ----------------------------------
> Apache Camel PMC Member
> Apache Karaf Committer
> Apache Servicemix Committer
> Email: ancosen1985@yahoo.com
> Twitter: @oscerd2
> Github: oscerd
>
>
>
> On Friday, September 23, 2016 4:15 PM, Daniel Kulp <dk...@apache.org> wrote:
>
> I think it’s too late to do this for 2.18 (trying to get that out soon). Might make sense for 2.19.
>
> Dan
>
>
>
>> On Sep 23, 2016, at 4:21 AM, Guillaume Nodet <gn...@apache.org> wrote:
>>
>> I'd like to start a discussion around upgrading Camel karaf support to
>> Karaf 4.
>> Karaf 4 has brought a number of changes that could be leveraged :
>> * no strong dependency on blueprint
>> * complete feature validation at build time
>> * more fine grained feature so that all dependencies can be expressed
>>
>> I'd like to leverage those for Camel. This can be achieved either by
>> dropping support for Karaf 2 and 3, or by keeping both (effectively
>> duplicating the integration code in platforms/karaf to platforms/karaf4).
>>
>> Also, it would make sense to upgrade to cxf 3.2-SNAPSHOT which I'm also
>> upgrading to Karaf 4.
>>
>> Thoughts ?
>> Guillaume Nodet
>
> --
> Daniel Kulp
> dkulp@apache.org <ma...@apache.org> - http://dankulp.com/blog <http://dankulp.com/blog>
> Talend Community Coder - http://coders.talend.com <http://coders.talend.com/
>>
Re: [DISCUSS] Upgrade Camel to Karaf 4
Posted by Andrea Cosentino <an...@yahoo.com.INVALID>.
I agree with Daniel.
Anyway this is something we can surely work on for the next release.
--
Andrea Cosentino
----------------------------------
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1985@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Friday, September 23, 2016 4:15 PM, Daniel Kulp <dk...@apache.org> wrote:
I think it’s too late to do this for 2.18 (trying to get that out soon). Might make sense for 2.19.
Dan
> On Sep 23, 2016, at 4:21 AM, Guillaume Nodet <gn...@apache.org> wrote:
>
> I'd like to start a discussion around upgrading Camel karaf support to
> Karaf 4.
> Karaf 4 has brought a number of changes that could be leveraged :
> * no strong dependency on blueprint
> * complete feature validation at build time
> * more fine grained feature so that all dependencies can be expressed
>
> I'd like to leverage those for Camel. This can be achieved either by
> dropping support for Karaf 2 and 3, or by keeping both (effectively
> duplicating the integration code in platforms/karaf to platforms/karaf4).
>
> Also, it would make sense to upgrade to cxf 3.2-SNAPSHOT which I'm also
> upgrading to Karaf 4.
>
> Thoughts ?
> Guillaume Nodet
--
Daniel Kulp
dkulp@apache.org <ma...@apache.org> - http://dankulp.com/blog <http://dankulp.com/blog>
Talend Community Coder - http://coders.talend.com <http://coders.talend.com/
>
Re: [DISCUSS] Upgrade Camel to Karaf 4
Posted by Daniel Kulp <dk...@apache.org>.
I think it’s too late to do this for 2.18 (trying to get that out soon). Might make sense for 2.19.
Dan
> On Sep 23, 2016, at 4:21 AM, Guillaume Nodet <gn...@apache.org> wrote:
>
> I'd like to start a discussion around upgrading Camel karaf support to
> Karaf 4.
> Karaf 4 has brought a number of changes that could be leveraged :
> * no strong dependency on blueprint
> * complete feature validation at build time
> * more fine grained feature so that all dependencies can be expressed
>
> I'd like to leverage those for Camel. This can be achieved either by
> dropping support for Karaf 2 and 3, or by keeping both (effectively
> duplicating the integration code in platforms/karaf to platforms/karaf4).
>
> Also, it would make sense to upgrade to cxf 3.2-SNAPSHOT which I'm also
> upgrading to Karaf 4.
>
> Thoughts ?
> Guillaume Nodet
--
Daniel Kulp
dkulp@apache.org <ma...@apache.org> - http://dankulp.com/blog <http://dankulp.com/blog>
Talend Community Coder - http://coders.talend.com <http://coders.talend.com/>