True, although I am not a huge fan is SPIFly and the complexity it adds
just to get services wired
Regards
Carsten
On 11/6/2026 9:52 AM, Stefan Seifert via dev wrote:
sound good to me - it will be a great benefit to get rid of that wrapper
bundle, and being able to freely update the dependency if a new johnzon version
is published.
stefan
-----Original Message-----
From: Konrad Windszus via dev <[email protected]>
Sent: Wednesday, November 4, 2026 11:34 AM
To: [email protected]
Cc: Konrad Windszus <[email protected]>
Subject: Deprecate Sling Commons Johnson
Hi,
Recent versions of Apache Johnson support OSGi with proper metadata for
OSGi Service Loader Mediator
(https://docs.osgi.org/specification/osgi.cmpn/8.0.0/service.loader.html),
compare with https://issues.apache.org/jira/browse/JOHNZON-108.
Although this requires deployment of SPI Fly
(https://aries.apache.org/documentation/modules/spi-fly.html) this is also
required by SLF4J 2.x (which is leveraging service loader as well).
Maintaining our own wrapper (https://github.com/apache/sling-org-apache-
sling-commons-johnzon) is therefore no longer necessary.
Sling Starter already ships with SPIFly and most other distributions I
know do as well meanwhile.
Any concerns with deprecating it following the procedure from
https://sling.apache.org/documentation/development/deprecating-sling-
modules.html and replace its usage in Sling Starter by Apache Johnson
directly (https://github.com/apache/sling-org-apache-sling-
starter/blob/64a72a361c09333ea423ebafbea01cb1418c83fe/src/main/features/bo
ot.json#L84)?
Thanks for your input,
Konrad
--
Carsten Ziegeler
Adobe
[email protected]