Mailing-List: contact dev-help@ace.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ace.apache.org
Received-SPF: pass (nike.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Message-ID: <528344A0.5070108@nanthrax.net>
Date: Wed, 13 Nov 2013 10:21:36 +0100
From: =?windows-1252?Q?Jean-Baptiste_Onofr=E9?= <jb@nanthrax.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: dev@ace.apache.org
Subject: Re: Towards a new release and baselining support...
References: <F479219E-4352-46C0-A409-7A5441A10758@luminis.nl>
In-Reply-To: <F479219E-4352-46C0-A409-7A5441A10758@luminis.nl>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable

Hi Marcel and the others,

+1 about that.

I'm pretty busy with Karaf 3.0.0, but I will take a look on latest=20
changes tomorrow.

Regards
JB

On 11/13/2013 10:17 AM, Marcel Offermans wrote:
> Hey guys,
>
> As you all know, a lot of things have happened recently within the ACE =
project. We=92ve rewritten the complete management agent, added quite a f=
ew features to the server and squashed bugs. With all of this work done I=
 feel we should start working towards a new release now, but I=92d like t=
o get everbody=92s opinion and check if there are things we forgot about =
that really need to make it into a new release.
>
> One thing I would like to do is to upgrade to the latest Bndtools 2.2.2=
 version and enable support for baselining. Baselining will give us a lot=
 of tool support to ensure our code (bundles and exported packages) is se=
mantically versioned. To leverage baselining support there are a couple o=
f things we need to do:
>
>   * We need the to start putting @ProviderType and @ConsumerType annota=
tions on all our APIs. In fact, we need to =93retrofit=94 this to our 1.0=
.0 release to ensure the baselining works correctly. These annotations ar=
e not magically available, but we can add them to the global build path (=
cnf/ext/defaults.bnd).
>
>   * We need to keep a copy of all released bundles (the latest version =
of each) in a repository to baseline against. Because we don=92t want our=
 build to break when we=92re off-line I propose we put them in a local re=
pository. We probably need to build those artifacts with the Eclipse comp=
iler to prevent problems that will otherwise occur because of differences=
 between ecj and javac so: checkout with Eclipse, build, collect all bund=
les from "generated" folders and publish them into the releaserepo in cnf=
. We also want to add them to the -deps artifact so people can easily get=
 started with a release with baselining enabled.
>
> If anybody else has input, speak up! :) WDYT?
>
> Greetings, Marcel
>

--=20
Jean-Baptiste Onofr=E9
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com