directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Karasulu <akaras...@apache.org>
Subject Re: [OSGi] Shared bundles update
Date Tue, 18 Jan 2011 19:23:35 GMT
Yeah I was thinking of using PAX Exam.

On Tue, Jan 18, 2011 at 4:06 PM, Jesse McConnell
<jesse.mcconnell@gmail.com> wrote:
> http://dev.eclipse.org/viewsvn/viewvc.cgi/jetty/trunk/jetty-osgi/test-jetty-osgi/?root=RT_JETTY
>
> that project there tests aspects of jetty running in an osgi
> environment...its not the easiest thing in the world to understand and
> it was setup by another committer (hugues) but it uses pax-exam which
> seems to be a fairly standard way to unit test osgi goop, it might
> help you here
>
> cheers,
> jesse
>
> --
> jesse mcconnell
> jesse.mcconnell@gmail.com
>
>
>
> On Sun, Jan 16, 2011 at 07:36, Alex Karasulu <akarasulu@apache.org> 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 <akarasulu@apache.org> 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
>>>
>>> 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.
>>>
>>> --
>>> [0] -- http://goo.gl/5WT5i
>>>
>>>
>>> Thanks,
>>> --
>>> Alex Karasulu
>>> My Blog :: http://www.jroller.com/akarasulu/
>>> Apache Directory Server :: http://directory.apache.org
>>> Apache MINA :: http://mina.apache.org
>>> To set up a meeting with me: http://tungle.me/AlexKarasulu
>>>
>>
>



-- 
Alex Karasulu
My Blog :: http://www.jroller.com/akarasulu/
Apache Directory Server :: http://directory.apache.org
Apache MINA :: http://mina.apache.org
To set up a meeting with me: http://tungle.me/AlexKarasulu

Mime
View raw message