carterkozak commented on pull request #650: URL: https://github.com/apache/logging-log4j2/pull/650#issuecomment-999860302
> How is that going to work for tests that set and clear properties? You don't want to set a property "forever"... Good question. I'm letting CI run our tests to see if there's anything that will need to be updated. Most of our tests rely on similar static state because binding a logging framework is itself static. Each test class (in the core project, anyhow) runs in an isolated fork, so per-test properties should be fine as long as we don't expect to change the value within a single test case. It shouldn't be any different from the tests which set properties like `log4j2.enable.threadlocals`/etc. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
