[ https://jira.qos.ch/browse/SLF4J-389?page=com.atlassian.jira.plugin.system.i... ] Ceki Gülcü commented on SLF4J-389: ---------------------------------- Hi [~hboutemy], Thank you for your explanations. My offer was to allow two extension points via {{renderThrowable()}} and {{renderLevel()}} methods saving the trouble of monkey patching and slightly improving the {{SimpleLogger}} code in the process. If you are interested in this limited refactoring, please create a separate JIRA issue. I'd be happy to follow through. Configuration is a different matter with a much larger scope. :)

SimpleLogger caches System.err and System.out ---------------------------------------------

Key: SLF4J-389 URL: https://jira.qos.ch/browse/SLF4J-389 Project: SLF4J Issue Type: Bug Affects Versions: 1.7.x Reporter: Igor Polevoy Assignee: Ceki Gülcü Fix For: 1.7.23

We usually use SimpleLogger in tests, and some other binding when running in production. In some cases, our tests depend on log values logged through the logger during a test. Unfortunately between version 1.7.0 and 1.7.1 this ability has been removed, since the SimpleLogger now caches the system stream in a static initialiser. Here is the code that broke this approach: https://github.com/qos-ch/slf4j/commit/996ccc7ca507994465c069554954ecb01890d... Basically, we would write a test: {quote}PrintStream err = System.err; PrintStream temp = new PrintStream(some buffer here); System.err = temp; // run tests System.err = err; // here we assert that the temp stream contains values we expect{quote} Unfortunately SimpleLogger now caches the system stream and never releases it, meaning swapping the streams to catch the output is not possible.

-- This message was sent by Atlassian JIRA (v7.3.1#73012)