+1 On Fri, Sep 23, 2016 at 11:47 AM, Andrea Cosentino < [email protected]> 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: [email protected] > Twitter: @oscerd2 > Github: oscerd > > > > On Friday, September 23, 2016 4:15 PM, Daniel Kulp <[email protected]> > 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 <[email protected]> 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 > [email protected] <mailto:[email protected]> - 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: [email protected] 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
