[slf4j-dev] [Bug 186] [patch] Enhanced SimpleLogger implementation

[bugzilla-daemon at pixie.qos.ch]

http://bugzilla.slf4j.org/show_bug.cgi?id=186

Michael Rumpf <michael at rumpfonline.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |michael at rumpfonline.de

--- Comment #4 from Michael Rumpf <michael at rumpfonline.de> 2011-02-13 17:07:34 CET ---
I also vote for this kind of bug. Without having the flexibility to turn on
output for all log levels this simple logger is almost useless.
I wanted to switch to the SLF4J API and in a first step I do not want to care
about which logging implementation to use. But in order to get all logging
statements printed I need to decide on an implementation or to change the
logger.debug statements to logger.info temporarily. Neither of those decisions
gets me started quickly with SLF4J. And if I still have the whole mess about
"how do I configure logging so that I get the output in Maven Surefire, in
Eclipse Launch configuration, in standalone Jetty, ..." then I can stick with
Jave Util Logging API because it comes with the JDK.

-- 
Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.