[
https://issues.apache.org/jira/browse/SLING-11906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17866418#comment-17866418
]
Julian Reschke edited comment on SLING-11906 at 7/16/24 2:36 PM:
-----------------------------------------------------------------
FYI, from <[https://www.slf4j.org/faq.html#changesInVersion200]>:
{quote}since 2.0.9 You can specify the provider class explicitly via the
"slf4j.provider" system property. This bypasses the service loader mechanism
for finding providers and may shorten SLF4J initialization.
{quote}
Maybe that makes things easier?
was (Author: reschke):
FYI, from <https://www.slf4j.org/faq.html#changesInVersion200>:
bq. since 2.0.9 You can specify the provider class explicitly via the
"slf4j.provider" system property. This bypasses the service loader mechanism
for finding providers and may shorten SLF4J initialization.
Maybe that makes things easiert?
> 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
> Assignee: 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)
