[
https://issues.apache.org/jira/browse/SLING-11906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17740111#comment-17740111
]
Konrad Windszus edited comment on SLING-11906 at 7/6/23 6:22 AM:
-----------------------------------------------------------------
Seems that was a deliberate decision from SLF4J, compare with
https://jira.qos.ch/browse/SLF4J-579?focusedId=21673&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-21673:
Maybe if we have a convincing use case for using the other packages outside of
logging backends we can adjust that.
Update: I added a comment in
https://jira.qos.ch/browse/SLF4J-579?focusedId=21735&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-21735
was (Author: kwin):
Seems that was a deliberate decision from SLF4J, compare with
https://jira.qos.ch/browse/SLF4J-579?focusedId=21673&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-21673:
Maybe if we have a convincing use case for using the other packages outside of
logging backends we can adjust that.
> 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)
