|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
I must admit the documentation is a bit unclear regarding the append attribute, which is actually inherited from FileAppender, where it can be either true or false – except in prudent mode, where append is automatically set to true. For RollingFileAppender, the attribute can only be true (see notes below for reasoning). And it's not a "mandatory attribute" (it does not need to be explicitly defined – the default value is true).
The release notes for this change:
...
Append mode is now mandatory in RollingFileAppender. This was already the default and truncation mode is unreasonable in most cases. For example, in truncate mode when an application stops and is quickly re-started, any pre-existing log file for the current period will be lost.