[logback-user] scanning property files that are read from configuration file
YSpotts at nexidia.com
Fri Nov 4 16:55:54 CET 2011
Thanks so much-- that is exactly what I am looking for. I put together a quick prototype and it looks to be working perfectly.
From: logback-user-bounces at qos.ch [mailto:logback-user-bounces at qos.ch] On Behalf Of ceki
Sent: Friday, November 04, 2011 11:07 AM
To: logback users list
Subject: Re: [logback-user] scanning property files that are read from configuration file
Property files are not watched for changes. I don't feel it is a widely needed feature so we probably won't implement it. However, you could write a property action which adds the property file to the list of scanned files.
Joran is not limited to the built-in rules. You can add new rules on the fly. See  for details. Don't hesitate to ask for help if you get stuck.
On 04/11/2011 3:36 PM, Yoel Spotts wrote:
> As described in the manual, one can set logback so that the logback
> config file is scanned for modifications by including the scan
> attribute on the <configuration> tag.
> However, if a property file is defined for property substitution with
> the <property> tag, that property file is NOT scanned for modifications.
> Is it possible to set up the property file to be scanned for changes?
> If not, can I make a feature request to add this ability - maybe add a
> "scan" attribute to the <property> tag which would add the property
> file to the Config watcher list.
> *Yoel Spotts*| Senior Software Engineer |nexidia
Logback-user mailing list
Logback-user at qos.ch
More information about the Logback-user