[FIXED JENKINS-21386] Allow reordering loggers, use first with matching ... #1091
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.
...name.
This change uses the top-most matching log recorder (based on name) to determine whether a log message should be added.
If both
com
(atINFO
) andcom.example
(atWARNING
) are defined for a specific log recorder, a log message in loggercom.example.Foo
will only be logged if it'sWARNING
orSEVERE
, or thecom
logger is above thecom.example
logger in the loggers list.This change will definitely impact existing configurations that start out with fairly restrictive log levels on e.g.
com
, to be more verbose with specific loggers later.This PR is one of two proposed solutions to JENKINS-21386, the other being #1090.