[
https://issues.apache.org/jira/browse/LOG4J2-1301?focusedWorklogId=264687&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-264687
]
ASF GitHub Bot logged work on LOG4J2-1301:
------------------------------------------
Author: ASF GitHub Bot
Created on: 21/Jun/19 14:42
Start Date: 21/Jun/19 14:42
Worklog Time Spent: 10m
Work Description: rgoers commented on issue #25: LOG4J2-1301 added
optionalMonitorFiles attribute for automatic reconf…
URL: https://github.com/apache/logging-log4j2/pull/25#issuecomment-504451158
In light of LOG4J2-494 and LOG4J2-913 this PR now has conflicts that would
have to be resolved. This functionality should be achievable through the
mechanisms implemented in those, although it doesn't specifically apply to
XInclude.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 264687)
Time Spent: 10m
Remaining Estimate: 0h
> Automatic reconfiguration with xml and xinclude
> -----------------------------------------------
>
> Key: LOG4J2-1301
> URL: https://issues.apache.org/jira/browse/LOG4J2-1301
> Project: Log4j 2
> Issue Type: Bug
> Affects Versions: 2.3
> Reporter: Alan Achtenberg
> Priority: Major
> Attachments: GroupFileConfigurationMonitor.java,
> MyXmlConfiguration.java, MyXmlConfigurationFactory.java
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Automatic reconfiguration does not work with xinclude/xml.
> Modifying xinclude files is not detected as a file change on on the main
> config file and as such it is not reconfigured when updates are made to files
> included with xinclude (ie. log4j2-appenders.xml).
> Desired functionality would be to also listen for changes of files that are
> included by main configuration file as well and update the configuration as
> needed.
> An alternative would be to allow user to specify additional files to monitor
> for changes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
