slf4j 2.0 (hence aio-lib-java 1.1.0) is not supported by sling/aem #182

Activity

1. francoisledroff

   added

   bugSomething isn't workingSomething isn't working

   on Sep 11, 2023
2. rombert commented on Sep 11, 2023

   

   rombert

   on Sep 11, 2023

   Member

   More actions

   From a Sling point of view it's a long way to SLF4j 2.0 compatibility because we have lots of consumers that are bound to slf4j 1.x because of their importing 'non-core' packages like org.slf4j.event or org.slf4j.helpers.

   I am wondering whether this bundle really needs slf4j 2.0 or whether it works with both 1.x and 2.x and can relax its import constraints.
3. bstopp commented on Oct 10, 2023

   

   bstopp

   on Oct 10, 2023

   Last edited by bstopp

   Collaborator

   More actions

   Maybe leave the top-level slf4j dependency version to be 2.x, but the AEM sub-package parent pom overrides it downgraded to 1.x?

   This way third party, non-aem uses can keep up-to-date, but the AEM bundles still deploy correctly to that context. Thoughts?
4. francoisledroff commented on Sep 2, 2024

   

   francoisledroff

   on Sep 2, 2024

   CollaboratorAuthor

   More actions

   closing this (should ahve done it a long time ago)
   as we downgraded sl4j to support aem see #185

   I created a follow up issue : #225
5. francoisledroff

   closed this as completedon Sep 2, 2024