Draft: Update log4j 1.x to log4j2 #34898
Closed
Conversation
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
Author
|
See #34877 |
|
Can one of the admins verify this patch? |
Member
|
I'd close this in favor of #34895 |
Member
|
+1 for @srowen 's comment. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
What changes were proposed in this pull request?
Update log4j 1.x to log4j2
Why are the changes needed?
log4j 1.x is no longer maintained, in case of critical issue, no way to quickly get a fix.
Does this PR introduce any user-facing change?
https://logging.apache.org/log4j/2.x/manual/migration.html
How was this patch tested?
Need more deep dive, but also need to finally get started about that (considering the recent events).