[
https://issues.apache.org/jira/browse/SLING-11906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17732009#comment-17732009
]
Robert Munteanu commented on SLING-11906:
-----------------------------------------
[~enorman] - ah, I scanned the description but missed the part where sl4j 2.0
exports both versions. I see that the o.a.s.commons.log bundle exports Logback
as well (
https://github.com/apache/sling-org-apache-sling-commons-log/blob/d88701405509a294c99aaf7211c7f4158feba860/bnd.bnd#L27-L28C38
) but I expect fewer consumers to be bound to it.
> 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.0.7 (and logback v1.4.7)
> 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)
