[
https://issues.apache.org/jira/browse/SLING-11906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18046275#comment-18046275
]
Manfred Baedke edited comment on SLING-11906 at 12/18/25 12:40 PM:
-------------------------------------------------------------------
[~cziegeler], [~rombert], [~jsedding]: I'm confused. How can the "all" bundle
work without a serviceloader mediator?
Edit: I suppose it's because logback and slf4j-api are both embedded, so the
bundle classloader can see a SLF4JServiceProvider directly?
cc [~reschke]
was (Author: baedke):
[~cziegeler], [~rombert], [~jsedding]: I'm confused. How can the "all" bundle
work without a serviceloader mediator?
cc [~reschke]
> 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
> Labels: Sling-14-ReleaseNotes
> 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)
