v2.21: Make setting logging level possible #14
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
Contributor
JakobMiksch
commented
Jun 20, 2022
•
JakobMiksch
commented
- makes it possible to set the logging level of GeoServer and if logging should be written to standard out
- fixes Make logging level configurable #12
- in GeoServer version 2.21 the logging has been rewritten (see https://geoserver.org/announcements/2022/05/24/geoserver-2-21-0-released.html#log4j-2-upgrade ) In contrast to the former GeoServer version 2.19 and 2.20 the built-in logging profiles can be used directly. No workaround like in v2.19: Make setting logging level possible #10 and v2.20: Make setting logging level possible #13 is necessary
JakobMiksch
changed the title
|
@chrismayer I rebased to the latest master and updated the README. This PR can be reviewed. |
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.