You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@aries.apache.org by Harald Wellmann <ha...@gmx.de> on 2011/06/17 18:51:33 UTC
org.osgi.service.blueprint Dependency
Looking at the Aries Blog sample sources, I noticed that almost all
bundles have an
Import-Package: org.osgi.service.blueprint
dependency, but I can see no such import in the Java sources.
Is this really required at runtime?
And if so, what makes the Maven Bundle Plugin include this dependency -
it doesn't seem to be in the compiled classes, and I can't see an
explicit configuration for this package.
Regards,
Harald
Re: org.osgi.service.blueprint Dependency
Posted by Alasdair Nottingham <no...@apache.org>.
Hi,
The OSGi specification for blueprint strongly advises all blueprint bundles
to import org.osgi.service.blueprint. As you note this isn't a code
dependency, but it is strongly encouraged. The maven bundle plugin inserts
it automatically if it sees you using blueprint. I expect you can disable it
by adding !org.osgi.service.blueprint into an <Import-Package> directive in
the configuration for the maven bundle plugin.
Alasdair
On 17 June 2011 17:51, Harald Wellmann <ha...@gmx.de> wrote:
> Looking at the Aries Blog sample sources, I noticed that almost all bundles
> have an
>
> Import-Package: org.osgi.service.blueprint
>
> dependency, but I can see no such import in the Java sources.
>
> Is this really required at runtime?
> And if so, what makes the Maven Bundle Plugin include this dependency - it
> doesn't seem to be in the compiled classes, and I can't see an explicit
> configuration for this package.
>
> Regards,
> Harald
>
--
Alasdair Nottingham
not@apache.org