Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id E7CC5200B8D for ; Fri, 23 Sep 2016 16:15:27 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id E6884160ACA; Fri, 23 Sep 2016 14:15:27 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 5D895160AC2 for ; Fri, 23 Sep 2016 16:15:27 +0200 (CEST) Received: (qmail 84224 invoked by uid 500); 23 Sep 2016 14:15:26 -0000 Mailing-List: contact dev-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list dev@camel.apache.org Received: (qmail 84212 invoked by uid 99); 23 Sep 2016 14:15:26 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Sep 2016 14:15:26 +0000 Received: from server.dankulp.com (unknown [104.128.68.137]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 231D11A01A7 for ; Fri, 23 Sep 2016 14:15:26 +0000 (UTC) From: Daniel Kulp Content-Type: multipart/alternative; boundary="Apple-Mail=_457A7F7C-BD2A-42FF-912C-EBC5AC4B34FD" Mime-Version: 1.0 (Mac OS X Mail 10.0 \(3226\)) Subject: Re: [DISCUSS] Upgrade Camel to Karaf 4 Date: Fri, 23 Sep 2016 10:15:22 -0400 References: To: dev@camel.apache.org In-Reply-To: Message-Id: <01E6E9EC-6840-4D40-9CBF-FAF35D6C5539@apache.org> X-Mailer: Apple Mail (2.3226) archived-at: Fri, 23 Sep 2016 14:15:28 -0000 --Apple-Mail=_457A7F7C-BD2A-42FF-912C-EBC5AC4B34FD Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 I think it=E2=80=99s 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 = wrote: >=20 > 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 >=20 > 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). >=20 > Also, it would make sense to upgrade to cxf 3.2-SNAPSHOT which I'm = also > upgrading to Karaf 4. >=20 > Thoughts ? > Guillaume Nodet --=20 Daniel Kulp dkulp@apache.org - http://dankulp.com/blog = Talend Community Coder - http://coders.talend.com = --Apple-Mail=_457A7F7C-BD2A-42FF-912C-EBC5AC4B34FD--