feat(logging): create global log4j config (#23631) #29694
Merged
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.
Proposed Changes
Issue #23631
As well as using a common configuration for tomcat and webapp logs. This also resolves an inconsistency when The logging class is referenced in code before the ContextLifecycleListener is called. Previously the wrong configuration contained in the resources classpath of the ant-tooling jar was picked up initially.
Tests
Further changes
There is follow up work to this PR that improves the way that the config can be specified and overridden. This change maintains the existing config file behavior but just applies it across the entire application.
Checklist
Additional Info
This PR resolves #23631 (create global log4j config).
Screenshots
This PR fixes: #23631