felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jackson, Bruce" <bru...@qualcomm.com>
Subject Re: felix subproject bundles without the compendium classes
Date Thu, 03 Feb 2011 12:18:47 GMT
Yes, correct.

For Android I have to be able to compile ate Android part of the app
against the osgi compendium jar with that on the app classpath, and then
export the compendium classes into the felix framework. If the same
packages appear in the bundles, you then run into the whole classloaders
problem.


On 03/02/2011 12:09, "Clement Escoffier" <clement.escoffier@gmail.com>
wrote:

>Hi,
>
>On 03.02.11 13:00, "Toni Menzel" <toni@okidokiteam.com> wrote:
>
>>You can change the bnd instructions inside the poms to do that.
>>For event, add org.osgi.service.event to the list of Import-Package.
>>
>>However, there has been a long debate of the pros and cons of including
>>interfaces into implementation bundles.
>>When exported correctly there is usually no big disadvantage other than
>>possibly wasted disk space.
>>On the other hand it much more consumer friendly to ship the interfaces,
>>too.
>>
>>So, do you really want to used forked versions of the felix bundles here
>>?
>
>I think it's for Android right ? In that case, no choice...
>
>Regards,
>
>Clement
>
>
>>
>>Toni
>>
>>On Thu, Feb 3, 2011 at 12:36 PM, Jackson, Bruce <brucej@qualcomm.com>
>>wrote:
>>
>>> Hi All
>>>
>>> Does anyone know if there are build flags that allow the felix
>>>subproject
>>> jars (for example eventadmin or http) to be built without including the
>>> org.osgi.* classes that from part of the standard compendium?
>>>
>>> Thanks
>>>
>>> Bruce
>>>
>>
>>
>>
>>-- 
>>*Toni Menzel - http://www.okidokiteam.com*
>
>


Mime
View raw message