Merged
Conversation
pavelhoral
force-pushed
the
upgrade-slf4j-to-2.x
branch
from
1f6fee0 to
9ba1537
Compare
pavelhoral
reviewed
Aug 6, 2025
kovaceviccz
force-pushed
the
upgrade-slf4j-to-2.x
branch
from
9ba1537 to
353c1e6
Compare
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
2 participants
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.
This PR addresses part of #214 by upgrading SLF4J to version 2.0.17, allowing Wren:AM deployments to use the latest versions of SLF4J logging backends, which now implement the ServiceLoader mechanism.
It introduces an
AMSlf4jServiceProviderwithin theopenam-slf4jmodule, replacing the oldStaticLoggerBinderclass.See https://www.slf4j.org/faq.html#changesInVersion200.