Github user cakofony commented on the issue:

    https://github.com/apache/logging-log4j2/pull/115
  
    @garydgregory The change in this PR does not cause the failure, the change 
that was merged instead introduced the bug.
    
    I have a repo here which I've used to reproduce the issue: 
https://github.com/cakofony/log4j2-composite-config-repro
    
    I'm not sure the best way to add such a test in this codebase (it gets a 
bit funky to write out a file, then modify it at runtime, and clean up). I can 
take a look at putting something together though


---

Reply via email to