Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[main] SLF4J 2 compatibility: avoid direct usage of StaticLoggerBinder (backport #11419) by @jfsoul #11429

Merged
merged 1 commit into from Sep 16, 2022

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Sep 16, 2022

This is an automatic backport of pull request #11419 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

StaticLoggerBinder is being removed in favour of ServiceLoader. Prefer the existing LoggerFactory.getILoggerFactory instead, which will delegate to StaticLoggerBinder in SLF4J 1, and ServiceLoader in SLF4J 2

Update documentation to replace direct references to StaticLoggerBinder

(cherry picked from commit 31f38ef)
@mergify mergify bot merged commit ac41ea4 into main Sep 16, 2022
@mergify mergify bot deleted the mergify/bp/main/pr-11419 branch September 16, 2022 11:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants