Tag LOG4J as origin of WARNING messages and use stderr instead of stdout #1761
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.
The "WARNING: sun.reflect.Reflection.getCallerClass is not supported. This will impact performance." gets a lot of attention [1]. Sometimes users are confused about its origin. Therefore identify LOG4J as the originator of the warning.
1: https://www.google.com/search?q=WARNING%3A+sun.reflect.Reflection.getCallerClass+is+not+supported.+This+will+impact+performance.&oq=WARNING%3A+sun.reflect.Reflection.getCallerClass+is+not+supported.+This+will+impact+performance.