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 74.125.82.178 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:reply-to:user-agent:mime-version:to:subject
         :references:in-reply-to:content-type:content-transfer-encoding;
        b=bBM8cezJLLwVlAdaP/NMzddcwwy/QHj7PgkwnxIbMZ4h7YG6AnUMc3+J5JJDv2hJTp
         +rXJKa/t4dW7Gz/xDzAUkvyE5H2WX/KtZcEJkSVE5+dOLYWV9S7QKJb2BFawN8obc8yv
         UdmCyM95reGA8qYsQywauNdyvQxeY84MF84PE=
Message-ID: <4D32F411.3040305@gmail.com>
Date: Sun, 16 Jan 2011 14:35:13 +0100
From: Emmanuel Lecharny <elecharny@gmail.com>
Reply-To: elecharny@apache.org
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US;
 rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: Re: [OSGi] Shared bundles update
References: <AANLkTi=pDfW_1euZbDkJ9+roS7zN+5Ntqw_XZr3ju04W@mail.gmail.com>
In-Reply-To: <AANLkTi=pDfW_1euZbDkJ9+roS7zN+5Ntqw_XZr3ju04W@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

On 1/16/11 12:53 PM, Alex Karasulu wrote:
> STATUS:
> ------------
>
> The following modules have been converted into bundles:
>
>      o i18n
>      o ldap
>      o ldap-client-api
>      o dsml-parser
>      o dsml-engine
>
> I will not bother with the following modules for reasons that should
> seem apparent:
>
>      o all
>      o integ

Great !!!
> The following modules still need to be made into bundles:
>
>      o ldap-schema
>
>
> ISSUES:
> -----------
>
> There seems to be some issues with the default operation of the
> maven-bundle-plugin where the schema file names are causing the plugin
> to barf. Here's something I had posted a couple years ago about the
> matter on felix-dev which seems still to be the case [0].
>
> Note the ldap-schema packages together schema LDIF files into the Jar.
> This is extracted out by a LdifExtractor class. The maven antrun
> plugin is used to build index files as well and the default jar
> archiver is used.
>
> This however probably can be solved by just generating the OSGi
> manifest with the bundle plugin and letting the current process using
> the jar archiver run without overwriting the manifest file.
>
> I'll play around with this.
>
>
> GOING FORWARD:
> --------------------------
>
> I guess we can start using the converted bundles in the studio build
> as direct dependencies. Also Pierre/Stefan could y'all update me on
> the steps we needed in the studio build to use the direct bundle
> dependency? That way I can update studio's build myself to use the
> ldap-schema bundle once it is complete. I also want to understand what
> steps are needed to change studio's build when we break out new
> bundles from inside shared-ldap.

Just a question : as it seems pretty easy to OSGify shared, why don't we 
do the same for ApacheDS modules too ?


-- 
Regards,
Cordialement,
Emmanuel L�charny
www.iktek.com