Return-Path: X-Original-To: apmail-karaf-dev-archive@minotaur.apache.org Delivered-To: apmail-karaf-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7292C11DDF for ; Wed, 18 Jun 2014 18:02:46 +0000 (UTC) Received: (qmail 77266 invoked by uid 500); 18 Jun 2014 18:02:46 -0000 Delivered-To: apmail-karaf-dev-archive@karaf.apache.org Received: (qmail 77226 invoked by uid 500); 18 Jun 2014 18:02:46 -0000 Mailing-List: contact dev-help@karaf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@karaf.apache.org Delivered-To: mailing list dev@karaf.apache.org Received: (qmail 77210 invoked by uid 99); 18 Jun 2014 18:02:46 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Jun 2014 18:02:46 +0000 Received: from localhost (HELO mail-oa0-f49.google.com) (127.0.0.1) (smtp-auth username gnodet, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Jun 2014 18:02:45 +0000 Received: by mail-oa0-f49.google.com with SMTP id i7so2632808oag.22 for ; Wed, 18 Jun 2014 11:02:45 -0700 (PDT) X-Received: by 10.60.101.170 with SMTP id fh10mr3480716oeb.39.1403114565103; Wed, 18 Jun 2014 11:02:45 -0700 (PDT) MIME-Version: 1.0 Received: by 10.182.116.200 with HTTP; Wed, 18 Jun 2014 11:02:24 -0700 (PDT) In-Reply-To: <53A1D034.4000302@nanthrax.net> References: <53A1C2A5.8070908@composent.com> <53A1D034.4000302@nanthrax.net> From: Guillaume Nodet Date: Wed, 18 Jun 2014 20:02:24 +0200 Message-ID: Subject: Re: Karaf 3,4 plans? To: dev Content-Type: multipart/alternative; boundary=089e010d8be83c6dea04fc20115a --089e010d8be83c6dea04fc20115a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I'd like to have a release or karaf 2.4 and a 4.0 beta during july. I think we should aim for a 4.0 soon in september maybe. 2014-06-18 19:45 GMT+02:00 Jean-Baptiste Onofr=C3=A9 : > Hi Scott, > > Karaf 3 uses: > - Felix Framework 4.2.1 > - Equinox 3.8.2 > > So it means full OSGi r4.3 support, and partial r5 support. > > I upgraded Karaf 4 to use Felix Framework 4.4.0 and Equinox 3.9.1, > providing a full OSGi r5 support. > > In term of release plan, I schedule Karaf 3.0.2 at least for end of next > week (we need some update of transitive projects for full Java8 support). > No plan for Karaf 4 for now. > > I would propose to prepare to r5 framework update for Karaf 3.0.3 (or > maybe on a 3.1.x branch, it would be better). > > Regards > JB > > > On 06/18/2014 06:47 PM, Scott Lewis wrote: > >> Hi Folks, >> >> I'm working on producing karaf features for ECF's upcoming Luna release >> (next week), and I'm wondering: should I target Karaf 3.0.1 or Karaf 4? >> >> I've seen discussion of Karaf 4 on this mailing list, but I couldn't >> find details of it on the karaf roadmap [1]. e.g. which OSGi framework >> version is going to be supported in 4 (i.e. which versions of Felix or >> Equinox are going to be used), as well as other new/added/changed >> features in karaf itself. It would also be nice to know some general >> release plans/schedule for 3.X and 4...if it's available. >> >> If possible, I would prefer to target both current and upcoming releases >> of karaf for the ECF R5 OSGi Remote Services impl being released June 25 >> [2], but there are some spec-imposed dependencies on framework versions >> (wiring API, etc), so it's helpful to know what the karaf 4 dependencies >> are going to be. >> >> Thanksinadvance for any info or plans pointers, >> >> Scott >> >> [1] https://cwiki.apache.org/confluence/display/KARAF/Roadmap >> [2] https://wiki.eclipse.org/Simultaneous_Release >> > > -- > Jean-Baptiste Onofr=C3=A9 > jbonofre@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com > --089e010d8be83c6dea04fc20115a--