Reword note on whitespace in Log4j settings

This commit rewords the note on whitespace in Log4j settings to not
refer to only of the examples on the page, but instead be clear that the
note applies to all the examples on the page.
This commit is contained in:
Jason Tedor 2017-04-20 07:34:16 -04:00
parent 7a934bd6f4
commit 446124b9d5
1 changed files with 2 additions and 2 deletions

View File

@ -134,8 +134,8 @@ appender.rolling.policies.time.modulate = true <6>
hours) hours)
NOTE: Log4j's configuration parsing gets confused by any extraneous whitespace; NOTE: Log4j's configuration parsing gets confused by any extraneous whitespace;
if you copy and paste the above settings, or enter any Log4j configuration in if you copy and paste any Log4j settings on this page, or enter any Log4j
general, be sure to trim any leading and trailing whitespace. configuration in general, be sure to trim any leading and trailing whitespace.
If you append `.gz` or `.zip` to `appender.rolling.filePattern`, then the logs If you append `.gz` or `.zip` to `appender.rolling.filePattern`, then the logs
will be compressed as they are rolled. will be compressed as they are rolled.