[slf4j-dev] [Bug 289] Add a NOOP method org.apache.log4j.Logger.setLevel() to enhance the bridging of Log4J over SLF4J
bugzilla-daemon at qos.ch
bugzilla-daemon at qos.ch
Wed Sep 4 13:15:11 CEST 2013
http://bugzilla.slf4j.org/show_bug.cgi?id=289
Robert Elliot <robert at teviotia.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |robert at teviotia.co.uk
--- Comment #2 from Robert Elliot <robert at teviotia.co.uk> ---
I think it should very much not be in the SLF4J API because it's not the right
level of abstraction - it mixes logging a statement (SLF4J's responsibility)
with controlling what actually happens to those log statements at runtime (the
implementation's responsibility).
As I see it the problem here is that code that should not be taking
responsibility for setting log levels is doing so. Adding the same function to
SLF4J would just encourage people to commit this kind of error using SLF4J as
well.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qos.ch/pipermail/slf4j-dev/attachments/20130904/cc432200/attachment.html>
More information about the slf4j-dev
mailing list