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/boot.json#L84)? Thanks for your input, Konrad
