[
https://issues.apache.org/jira/browse/SLING-11906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17810474#comment-17810474
]
Konrad Windszus edited comment on SLING-11906 at 1/24/24 3:57 PM:
------------------------------------------------------------------
The fix in SLF4J 2.0.11 only exports {{org.slf4j.helpers}} in a backwards
compatible way
(https://github.com/qos-ch/slf4j/commit/02b36a269a9b13dac435699839f3200529dd0e10).
I think we should get rid of imports towards {{org.sl4j.event}} as that was
IMHO never devised as stable API (but only supposed to be used internally).
was (Author: kwin):
The fix in SLF4J 2.0.11 only exports {{org.slf4j.helpers}} in a backwards
compatible way. I think we should get rid of imports towards {{org.sl4j.event}}
as that was IMHO never devised as stable API (but only supposed to be used
internally).
> Migrate to slf4j 2.x
> --------------------
>
> Key: SLING-11906
> URL: https://issues.apache.org/jira/browse/SLING-11906
> Project: Sling
> Issue Type: Improvement
> Reporter: Eric Norman
> Priority: Major
> Fix For: Commons Log 6.0.0
>
>
> Increasingly more libraries have been migrating to slf4j 2.x (for example
> logback 1.3+, tika 2.5+ and jetty 10+)
> To be compatible with those, the sling commons log bundle should migrate to
> slf4j v2.x (and logback v1.4.x or v1.3.x?)
> It looks like slf4j 2.x exports both 2.x and 1.7.36 versions of the exported
> packages, so it should hopefully be compatible with existing bundles that are
> importing the 1.x version of the slf4j packages.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
