Issue #14435 - Bump OSGi min version for slf4j imports#14497
Merged
Conversation
sbordet
approved these changes
Mar 2, 2026
olamy
approved these changes
Mar 2, 2026
sbordet
pushed a commit
that referenced
this pull request
Mar 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bump the version range of slf4j in OSGi from
1.7 ... 3.0to2.0 ... 3.0We can no longer support slf4j-api 1.7.x, since we started using the
Logger.atInfo()andLogger.atDebug()APIs as part of issue #13884We've been using slf4j 2.x since Jetty 10.0.0.
Thing is, we started by using slf4j 2.0.0.alpha releases, due it having a proper JPMS declaration / support.
This use of an alpha version of 2.0.0 was a problem for OSGI back in 2021.
See:
Since there's been several non-alpha releases of slf4j 2.0.x so far, this PR is undoing the down-versioning from that past issue.
Resolves: #14435