You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by Jörg Hoh <jh...@googlemail.com> on 2026/03/04 17:18:16 UTC

Future of o.a.servicemix dependencies

Hi,

I recently tried a PR to the servicemix project to update a specific
wrapped bundle, but I was told that servicemix is not maintaining
these bundles anymore
(https://github.com/apache/servicemix-bundles/pull/307#issuecomment-3921797507).

In Sling we have a series of servicemix dependencies, for example:

org.apache.servicemix.bundles : org.apache.servicemix.bundles.hamcrest
org.apache.servicemix.bundles : org.apache.servicemix.bundles.rhino
org.apache.servicemix.bundles : org.apache.servicemix.bundles.kafka-clients
org.apache.servicemix.bundles : org.apache.servicemix.bundles.thymeleaf
org.apache.servicemix.bundles : org.apache.servicemix.bundles.ognl
org.apache.servicemix.bundles : org.apache.servicemix.bundles.jasypt
org.apache.servicemix.bundles : org.apache.servicemix.bundles.okio
org.apache.servicemix.bundles : org.apache.servicemix.bundles.okhttp
org.apache.servicemix.specs : org.apache.servicemix.specs.jaxp-api-1.4
org.apache.servicemix.specs : org.apache.servicemix.specs.activation-api-2.0.1

we potentially can avoid a few of those bundles (e.g. replace okhttp
with the apache http client), but at least for the specs this is not
possible.
The only option I see is to maintain these bundles on our own (we can
probably use the exact same approach servicemix used).

WDYT?
Jörg

-- 
https://cqdump.joerghoh.de

RE: Future of o.a.servicemix dependencies

Posted by Stefan Seifert <st...@diva-e.com>.
if the spec did not change, we don't have to replace the bundles.
geronimo maintains a lot of spec bundles as well:
https://repo1.maven.org/maven2/org/apache/geronimo/specs/
but looking at https://github.com/apache/geronimo-specs, the last release is from 2019, so looks rather unmaintained as well.

we also should check the latest version of the jars those bundles are wrapping - often they were enabled for OSGi in more recent versions, so we could just replace the wrapper bundle with the real jar.

maintaining those wrappers on our side should only be the last resort.

stefan

> -----Original Message-----
> From: Jörg Hoh <jh...@googlemail.com>
> Sent: Wednesday, March 4, 2026 6:18 PM
> To: Sling Developers List <de...@sling.apache.org>
> Subject: Future of o.a.servicemix dependencies
> 
> Hi,
> 
> I recently tried a PR to the servicemix project to update a specific
> wrapped bundle, but I was told that servicemix is not maintaining
> these bundles anymore
> (https://github.com/apache/servicemix-bundles/pull/307#issuecomment-
> 3921797507).
> 
> In Sling we have a series of servicemix dependencies, for example:
> 
> org.apache.servicemix.bundles : org.apache.servicemix.bundles.hamcrest
> org.apache.servicemix.bundles : org.apache.servicemix.bundles.rhino
> org.apache.servicemix.bundles : org.apache.servicemix.bundles.kafka-
> clients
> org.apache.servicemix.bundles : org.apache.servicemix.bundles.thymeleaf
> org.apache.servicemix.bundles : org.apache.servicemix.bundles.ognl
> org.apache.servicemix.bundles : org.apache.servicemix.bundles.jasypt
> org.apache.servicemix.bundles : org.apache.servicemix.bundles.okio
> org.apache.servicemix.bundles : org.apache.servicemix.bundles.okhttp
> org.apache.servicemix.specs : org.apache.servicemix.specs.jaxp-api-1.4
> org.apache.servicemix.specs : org.apache.servicemix.specs.activation-api-
> 2.0.1
> 
> we potentially can avoid a few of those bundles (e.g. replace okhttp
> with the apache http client), but at least for the specs this is not
> possible.
> The only option I see is to maintain these bundles on our own (we can
> probably use the exact same approach servicemix used).
> 
> WDYT?
> Jörg
> 
> --
> https://cqdump.joerghoh.de