Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (athena.apache.org: domain of elecharny@gmail.com
 designates 209.85.212.176 as permitted sender)
Message-ID: <5481492A.4070404@gmail.com>
Date: Fri, 05 Dec 2014 06:56:58 +0100
From: =?UTF-8?B?RW1tYW51ZWwgTMOpY2hhcm55?= <elecharny@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
 rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: Re: Validation of ApacheDS OSGi bundles
References: <547E0835.8070603@stefan-seelmann.de>
In-Reply-To: <547E0835.8070603@stefan-seelmann.de>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Le 02/12/14 19:43, Stefan Seelmann a écrit :
> Hi all,
>
> As you know we try to migrate Studio to Tycho build, and always want to
> use the latest and greates build of JDBM, Mavibot, API, and ApacheDS. It
> happened the released artifacts are no valid OSGi bundles or have
> invalid MANIFEST.MF. But even worse is that in the Tycho build the error
> messages are not really explicit, it is very hard to find the problem.
>
> What I dream from is to have some mechanism to avoid that problems and
> to identify OSGi related problems early. I don't have enough knowledge
> which tools exists out there, so maybe an OSGi export can help.
>
> First idea I have is to have a test that checks that each single
> artifact is a valid bundle.
>
> Second thing would be some kind of integration test that starts an OSGi
> runtime (preferred both Equinox and Felix/Karaf) and installs all
> ApacheDS bundles, to verify that all dependencies can be resolved.
>
> Third idea would be to even startup ApacheDS in that runtime, but maybe
> that requires more work.
>
> Any ideas or further suggestions are welcomed.
>
> Kind Regards,
> Stefan


What about http://www.aqute.biz/Bnd/CommandLine ?