Updating log4j properties file in zuul-sample #1068
Merged
Conversation
This file contains 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
argha-c
approved these changes
May 21, 2021
|
@kashish9034z merged, thanks! |
argha-c
pushed a commit
to argha-c/zuul
that referenced
this pull request
Mar 22, 2022
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.
What is the Issue ?
Existing log4j properties file is not being picked by log4j and there are no logs produced to console.
Why does this issue exist ?
Log4j2 uses a different format of properties file which is explained on apache's website
ChangeLog-
@argha-c Addressed your comments. Previous PR got closed because of forced-push