I don't think that's a good idea to import the osgi api.

It may lead to problems if multiple blueprint implementations are
deployed for some reason.
To support such a case, the blueprint bundles are supposed to import
the org.osgi.blueprint package iirc, so that the osgi framework wiring
will be correctly split and only the blueprint extender which has been
imported will actually extend the bundle.  By importing the api, two
extenders can then be compatible and both would extend the bundle.

IF the main reason is that people have the compendium bundle deployed,
well, that's a bad idea because the same problem also tend to apply
with other osgi services such as ConfigAdmin and others which usually
ship their own version of the package.


On Fri, May 18, 2012 at 7:42 PM,  <[email protected]> wrote:
> Author: dkulp
> Date: Fri May 18 17:42:46 2012
> New Revision: 1340184
>
> URL: http://svn.apache.org/viewvc?rev=1340184&view=rev
> Log:
> Import the osgi blueprint stuff so it can work with a wider range of 
> containers
>
> Modified:
>    aries/branches/blueprint-0.3.2-fixes/blueprint-bundle/pom.xml
>
> Modified: aries/branches/blueprint-0.3.2-fixes/blueprint-bundle/pom.xml
> URL: 
> http://svn.apache.org/viewvc/aries/branches/blueprint-0.3.2-fixes/blueprint-bundle/pom.xml?rev=1340184&r1=1340183&r2=1340184&view=diff
> ==============================================================================
> --- aries/branches/blueprint-0.3.2-fixes/blueprint-bundle/pom.xml (original)
> +++ aries/branches/blueprint-0.3.2-fixes/blueprint-bundle/pom.xml Fri May 18 
> 17:42:46 2012
> @@ -40,7 +40,6 @@
>         </aries.osgi.activator>
>         <aries.osgi.import>
>             !org.apache.aries.blueprint*,
> -            !org.osgi.service.blueprint*,
>             org.eclipse.osgi.internal.loader;resolution:=optional,
>             org.eclipse.osgi.framework.internal.core;resolution:=optional,
>             org.eclipse.osgi.framework.adaptor;resolution:=optional,
>
>



-- 
------------------------
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
FuseSource, Integration everywhere
http://fusesource.com

Reply via email to