You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Robert Munteanu (Jira)" <ji...@apache.org> on 2023/06/12 13:38:00 UTC

[jira] [Commented] (SLING-11906) Migrate to slf4j 2.x

    [ https://issues.apache.org/jira/browse/SLING-11906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17731620#comment-17731620 ] 

Robert Munteanu commented on SLING-11906:
-----------------------------------------

I think we should have a way of supporting slf4j 1.x and 2.x at the same time. We probably have lots of consumers bound to the old version of the slf4j api.

> 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)