directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Emmanuel Lecharny <>
Subject Re: [OSGi] Shared bundles update
Date Sun, 16 Jan 2011 13:35:13 GMT
On 1/16/11 12:53 PM, Alex Karasulu wrote:
> ------------
> 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
> -----------
> 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.
> --------------------------
> 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 ?

Emmanuel L├ęcharny

View raw message