[ http://jira.qos.ch/browse/LBCLASSIC-245?page=com.atlassian.jira.plugin.syste... ] Ceki Gulcu edited comment on LBCLASSIC-245 at 2/10/11 10:49 PM: ---------------------------------------------------------------- Fixed in v0.9.28, http://github.com/ceki/logback/commit/d411638322b2a2291ac Setting scan attribute to true in <configuration> element cascades to included files. was (Author: noreply.ceki@qos.ch): Fixed in http://github.com/ceki/logback/commit/d411638322b2a2291ac
Need to scan included files ---------------------------
Key: LBCLASSIC-245 URL: http://jira.qos.ch/browse/LBCLASSIC-245 Project: logback-classic Issue Type: New Feature Reporter: Geoffrey Assignee: Logback dev list Priority: Minor Fix For: 0.9.28
I'm using the following configuration and I'm looking for a method to scan included files. <configuration scan="true" scanPeriod="10 seconds"> <insertFromJNDI env-entry-name="java:comp/env/logback-file" as="logback-file" /> <contextName>lala</contextName> <include file="${logback-file}" /> </configuration> Once scan directive is used, logback is going to rescan this file every 10 seconds whether its modification date has changed. The issue is that I have to overwrite the previous file in order to rescan the target ${logback-file}. I suggest adding an attribute in the configuration marker in order to force logback to scan included files . It could be something like that: <configuration scan="true" scanPeriod="10 seconds" scanIncluded="true"> ..... </configuration> In order to process this task, at each scan logback should memorize the reference to the included files, and their latest modification date. Consequently, every 10 seconds, logback check the whole list of files and rescan the main file if something has changed.
-- 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