Both the maven-bundle-plugin and the bnd-maven-plugin will precess the standard
DS annotations for you.
Regards,
Tim
> On 16 Aug 2017, at 14:30, alexander.sah...@brodos.de wrote:
>
> Hello Tim.
>
> How am I to use DS with @Component annotaition when having
> blueprint-maven-plugin in place!
Hello Tim.
How am I to use DS with @Component annotaition when having
blueprint-maven-plugin in place!
Is it possible anyways?
Regards,
Alexander.
>>>
Hi Tim.
Well, maybe I made myself not completely clear. Of course it is
possible to mix DS and blueprint even in the same bundle when you use
Hi Tim.
Well, maybe I made myself not completely clear. Of course it is
possible to mix DS and blueprint even in the same bundle when you use
services for communication but as you say, it's normally not a good
idea.
> Mixing blueprint and DS in the same bundle isn’t
> normally a good idea, but
Hi Alexander,
> Using DS is currently not an option as the whole project uses blueprint and
> the mix of DS and blueprint is not recommended as far as I know.
By whom and why? OSGi services are OSGi services, it doesn’t matter which
framework you use to register or consume them. I regularly
Hello Tim.
Thanks for the quick response and the clarification. In fact it's
exactly like you described. My intention is to postpone the
STARTING/ACTIVE state until a certain requirement is fulfilled.
Using DS is currently not an option as the whole project uses blueprint
and the mix of DS and
Hi Alexander,
An active time capability is ignored by the OSGi framework. This means that it
will not prevent your OSGi bundle moving from the INSTALLED state to the
RESOLVED state.
What you’re seeing is that the resolver can also be run elsewhere, for example
to find or validate a set of
Hi there.
According to
http://osgi-dev.mail.osgi.narkive.com/GfJqfPGZ/require-capability-osgi-service-filter-effective-active-and-blueprint
(and the OSGi spec), a R-C header with effective:=active should be ignored by
OSGi framework. But when I create a R-C header like
Require-Capability:
