[prev in list] [next in list] [prev in thread] [next in thread] 

List:       logback-dev
Subject:    [logback-dev] [JIRA] Resolved: (LBCLASSIC-245) Need to scan
From:       "Ceki Gulcu (JIRA)" <noreply-jira () qos ! ch>
Date:       2011-01-24 21:49:51
Message-ID: 107884603.1295905791322.JavaMail.ceki () pixie
[Download RAW message or body]


     [ http://jira.qos.ch/browse/LBCLASSIC-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Ceki Gulcu resolved LBCLASSIC-245.
----------------------------------

    Fix Version/s: 0.9.28
       Resolution: Fixed

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

        
_______________________________________________
logback-dev mailing list
logback-dev@qos.ch
http://qos.ch/mailman/listinfo/logback-dev


[prev in list] [next in list] [prev in thread] [next in thread]