Glad to hear that your are making progress. If you wish, you could place your changes in a fork of my github repository [1], then others might be able to see and benefit from your changes. [1] https://github.com/ceki/logback/ On 04/11/2011 4:55 PM, Yoel Spotts wrote:
Ceki,
Thanks so much-- that is exactly what I am looking for. I put together a quick prototype and it looks to be working perfectly.
Thanks!
Yoel
-----Original Message----- From: logback-user-bounces@qos.ch [mailto:logback-user-bounces@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
Hi Yoel,
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 [1] for details. Don't hesitate to ask for help if you get stuck.
-- Ceki http://twitter.com/#!/ceki
[1] http://logback.qos.ch/manual/onJoran.html#newRule
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.
Thanks!
*Yoel Spotts*| Senior Software Engineer |nexidia
-- Ceki http://twitter.com/#!/ceki