commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Sicker <boa...@gmail.com>
Subject Re: [all][osgi] how to deal with non-bundle dependencies?
Date Tue, 02 May 2017 15:56:06 GMT
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.

On 2 May 2017 at 02:30, Stefan Bodewig <bodewig@apache.org> wrote:

> Hi all
>
> I must admit I've never been a fan of OSGi and likely don't know enough
> about it.
>
> Compress like many of the components around here is an OSGi bundle and I
> recall I submitted a trivial patch to XZ for Java - our only dependency
> as of now - to turn it into a bundle as well.
>
> How does one deal with adding dependencies on jars that are not bundles?
> Is it possible at all?
>
> A quick search seems to imply we'd either have to bundle the dependency
> jar with ours or turn it into a bundle ourselves (by wrapping it).
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>


-- 
Matt Sicker <boards@gmail.com>

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