[slf4j-dev] [Bug 110] Create a bridge between System.out/System.err and SLF4J
bugzilla-daemon at pixie.qos.ch
bugzilla-daemon at pixie.qos.ch
Thu Apr 16 12:09:28 CEST 2009
http://bugzilla.slf4j.org/show_bug.cgi?id=110
Ceki Gulcu <listid at qos.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |listid at qos.ch
Status|NEW |ASSIGNED
--- Comment #2 from Ceki Gulcu <listid at qos.ch> 2009-04-16 12:09:28 ---
Hi Robert,
Thank you for this contribution. I quite like the ideas present in your code,
in particular, the ability to detect that LogPrintStream is being invoked by
Throwable. Allowing the logging framework, e.g. log4j, to still access the
original console is also quite smart.
>From what I could gather, the code does not aggregate the various print(s)
calls made to LogPrintStream by Throwable.printStackTrace() method into a
single log statement. You already have some of the logic to do that. Would you
care to add the ability to aggregate multiple print(s) calls made by Throwable
into a single log statement?
Since this contribution is on the substantial side, may I ask you to file an
ICLA? See http://logback.qos.ch/cla.txt for details.
--
Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the slf4j-dev
mailing list