directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pierre-Arnaud Marcelot>
Subject Re: [OSGi] Shared bundles update
Date Mon, 17 Jan 2011 13:39:56 GMT
Hi Alex,

Thanks for converting the modules into bundles.

I took some extra steps [1] [2] (the same ones as for the i18n modules) to make the bundle
fully compatible with Studio's build:
- Generation of the MANIFEST.MF file in a top level META-INF folder (ignored by SVN)
- Usage of ${} instead of ${} for Maven 3 compliance
- Removal of Bundle-Version directive which is inherited automatically from the project version
- Usage of ${} as Bundle-Name (instead of ${project.artifactId})

After fixing an issue with a wrong version used in Studio for Commons Lang (2.3 instead of
2.5) I was able to replace Studio's libraries plugins of Shared by the OSGI-fied Shared dependencies
within Eclipse.
Studio seems to work like a charm. :)

I think we should also turn the 'all' module as a bundle. It's pretty easy and doesn't harm
to do it.


[1] -
[2] -

On 16 janv. 2011, at 14:36, Alex Karasulu wrote:

> The conversion of ldap-schema into a bundle is complete but I want to
> test it in the OSGi environment to make sure it's working properly.
> Might setup an integration test using felix in the shared-integ module
> and make sure the module only runs with an -Dintegration flag/profile.
> Is it worth turning the 'all' module, shared-all, into a bundle as
> well? Thoughts?
> Regards,
> Alex
> On Sun, Jan 16, 2011 at 1: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
>> 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.
>> --
>> [0] --
>> Thanks,
>> --
>> Alex Karasulu
>> My Blog ::
>> Apache Directory Server ::
>> Apache MINA ::
>> To set up a meeting with me:

View raw message