[logback-dev] [JIRA] Created: (LBCORE-191) When rolled file directory is not defined always by deafult use same directory for rolled file as for log file being rolled
Stevo Slavic (JIRA)
noreply-jira at qos.ch
Thu Jan 13 02:20:51 CET 2011
When rolled file directory is not defined always by deafult use same directory for rolled file as for log file being rolled
---------------------------------------------------------------------------------------------------------------------------
Key: LBCORE-191
URL: http://jira.qos.ch/browse/LBCORE-191
Project: logback-core
Issue Type: Improvement
Components: Rolling
Affects Versions: 0.9.27
Reporter: Stevo Slavic
Assignee: Logback dev list
Priority: Minor
E.g. if FileNamePattern of ch.qos.logback.core.rolling.TimeBasedRollingPolicy is configured to "webapp.%d{yyyy-MM-dd}.log.zip" and File of ch.qos.logback.core.rolling.RollingFileAppender is configured to "/var/log/tomcat6/webapp.log", then rolled file should be created in /var/log/tomcat6 directory and not in current working directory.
This is to keep config DRY in cases when log and it's rolled fragments should be stored in same directory.
This behavior is consistent with case when both File and FileNamePattern don't define directory, just extends this behavior to the case when File has directory defined, and FileNamePattern doesn't.
Related logback-users mailing list discussion reference: http://markmail.org/message/k6ezjx5lqitwvoy4
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the logback-dev
mailing list