[slf4j-dev] [Bug 150] LogManager is needed but not implemented yet

bugzilla-daemon at pixie.qos.ch bugzilla-daemon at pixie.qos.ch
Fri Oct 9 15:08:50 CEST 2009


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


Rick Beton <rick.beton at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |




--- Comment #4 from Rick Beton <rick.beton at gmail.com>  2009-10-09 15:08:49 ---
Sorry for the late reply.

I have legacy code using only LogManager's

void resetConfiguration()
Logger getRootLogger()

In my case, it would be sufficent to implement an empty method for
resetConfiguration(), although I don't know whether this would be good general
solution. getRootLogger() must return a non-null logger.

A synopsis of the legacy code is:

LogManager.resetConfiguration();
Logger rootLogger = LogManager.getRootLogger();
rootLogger.setLevel(Level.WARN);

(Unfortunately, this code cannot be modified because it is expected to continue
to work with Log4J also.)

Thanks.


-- 
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