One of the advantages of Logback is that it's possible to change the configuration on the fly, during application run, and therefore it's perfect to change log levels for debugging purposes, etc.
Is it possible to declare the scan period for the LogbackConfig.groovy file (or the logback = {} closure)?
Here's the link to the Logback Documentation for this feature: http://logback.qos.ch/manual/configuration.html#autoScan
Edit
As a "workaround" would it be possible to work with the External Config Reload Plugin (https://github.com/adaptivecomputing/grails-external-config-reload) which fires an onConfigChange Event if an external config file got updated?
Is it possible to implement the onConfigChange Event (hook)?
One of the advantages of Logback is that it's possible to change the configuration on the fly, during application run, and therefore it's perfect to change log levels for debugging purposes, etc.
Is it possible to declare the
scanperiod for theLogbackConfig.groovyfile (or thelogback = {}closure)?Here's the link to the Logback Documentation for this feature: http://logback.qos.ch/manual/configuration.html#autoScan
Edit
As a "workaround" would it be possible to work with the External Config Reload Plugin (https://github.com/adaptivecomputing/grails-external-config-reload) which fires an
onConfigChangeEvent if an external config file got updated?Is it possible to implement the
onConfigChangeEvent (hook)?