chore: migrate logging to slf4j + logback - #1823
Merged
Merged
Conversation
olovy
requested review from
andersju,
jannistsiroyannis,
kaipoykio,
kwahlin,
lrosenstrom and
niklasl
August 7, 2026 12:25
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.
log4j 1.x is EOL since 2015...
There exists a binary compatible fork of log4j 1.2 with security fixes.
Let's switch to the more or less standard slf4j instead. And use logback as logging backend.
Verified log output on dev2.
There is some additional noise when running unit tests. But I think we can deal with that separately.