Hi, Eric has been working on a large PR to move our commons.log bundle to slf4j 2.0 . I think this is a very welcome improvement.
The only open topic (for me) is the new requirement of using the Aries SPIFly bundle. Slf4j 2.0 is now using the ServiceLoader mechanism to discover logging implementations and the OSGi answer to that is SPIFly. SPIFly is unfortunately heavy on dependencies and will need to be started very early on for logging to be functional. We have historically tried to avoid it, for example by creating our Johnzon wrappers. This might be more important for implementations like sling- mini. The details about the requirements start at [1] and I would encorage anyone that has an idea (or the cycles to implement a solution) to do so on the PR. I think supporting slf4j 2.x with the SPIFly requirement is better than slf4j 1.x without SPIFly, but maybe we can avoid it entirely. Patches welcome ;-) Thanks, Robert [1]: https://github.com/apache/sling-org-apache-sling-commons-log/pull/18#issuecomment-2088735403
