Thank you all. This has been very helpful. :-)
___
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev
ce, this
>>> is still useful to OSGi code in many instances where you don't have a
>>> service lifecycle.
>>>
>>> Gruss
>>> Bernd
>>> --
>>> http://bernd.eckenfels.net
>>> --
>>> *Von:* osgi-de
gt; An alternative is, to just have the bundle headers and no service, this
>> is still useful to OSGi code in many instances where you don't have a
>> service lifecycle.
>>
>> Gruss
>> Bernd
>> --
>> http://bernd.eckenfels.net
>>
> Auftrag von David Leangen via osgi-dev
> *Gesendet:* Thursday, May 21, 2020 12:44:04 AM
> *An:* osgi-dev@mail.osgi.org
> *Betreff:* [osgi-dev] Library development
>
> Hi!
>
> What is the best way to prepare a library to OSGi-compatible, but not
> force the use of OSGi
Hi Bernd,
Thank you, this is good information. Much appreciated.
Would you happen to have a link to an example project?
Cheers,
=David
___
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev
s.net
Von: osgi-dev-boun...@mail.osgi.org im Auftrag
von David Leangen via osgi-dev
Gesendet: Thursday, May 21, 2020 12:44:04 AM
An: osgi-dev@mail.osgi.org
Betreff: [osgi-dev] Library development
Hi!
What is the best way to prepare a library to OSGi-compatible
Hi!
What is the best way to prepare a library to OSGi-compatible, but not force the
use of OSGi (including forcing transitive dependencies)?
The library should be split into api / implementation and offered as a service,
but it should be possible for those who do not use OSGi to obtain the
imp
