Eyal Roth created LOGBACK-1408:
--
Summary: Reconfigure with scan feature ignores changes made to
JoranConfigurator
Key: LOGBACK-1408
URL: https://jira.qos.ch/browse/LOGBACK-1408
Project: logback
Issue Type: Bug
Affects Versions: 1.1.7
Reporter: Eyal Roth
Assignee: Logback dev list
Whatever changes made problematically to {{JoranConfigurator}} prior to loading
the configuration are being ignored by the re-configuration introduced in the
"scan" feature.
The code at {{ReconfigureOnChangeTask}} creates a new configurator and also
resets the context, which may contain some desired settings for the
configurations - say, substitution properties discovered only at runtime.
The official documentation [clearly
states|https://logback.qos.ch/manual/configuration.html#joranDirectly] that
modifying the configurator manually is a valid way to go with, so this is why
this is considered a bug IMHO.
I'm seeing multiple issues which are most likely related to this problem:
LOGBACK-485, LOGBACK-592, LOGBACK-1059.
I ended up dumping the scan feature and implementing on my own using Java's
{{WatchService}} (LOGBACK-1073).
--
This message was sent by Atlassian JIRA
(v7.3.1#73012)
___
logback-dev mailing list
logback-dev@qos.ch
http://mailman.qos.ch/mailman/listinfo/logback-dev
