commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Sicker <>
Subject Re: [all][osgi] how to deal with non-bundle dependencies?
Date Thu, 04 May 2017 14:11:11 GMT
Without a container, the "easy" way would be to embed Felix and start up
the OSGi framework itself. The easiest way to do this in unit tests would
be using something like Pax Exam <>.

On 4 May 2017 at 01:11, Stefan Bodewig <> wrote:

> On 2017-05-02, Matt Sicker wrote:
> > Apache ServiceMix tends to repackage a lot of 3rd party libraries as
> > bundles, so that's one method. End users can use things like bnd to
> > generate a manifest for 3rd party jars (e.g., installing jars using the
> > "wrap:" URI in Apache Karaf), though that's kind of similar to
> automodules
> > in JPMS which isn't the best thing.
> In our case with org.brotli:dec at Compress the "automodules" approach
> would be good enough. The whole library has a single public class and no
> dependencies, the bundle definition would be trivial.
> We've now marked the dependency with "resolution:=optional" and hope
> this allows Compress to remain a valid bundle. Do you know whether there
> is an easy way to test whether a library would work as a bundle without
> actually trying to deploy an application using it into a container?
> Stefan
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Matt Sicker <>

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message