Not really - setting a level is implementation specific, a valid SLF4J implementation might not even allow setting levels on a Logger. A library should not be doing it anyway - what level of messages the end application is interested in doing something with should be the business of the end application, not the library.
If it's the end application code that wants to dynamically set the level then that bit of code should be ported to whatever SLF4J implementation you are planning on using. Rob On 7 Jan 2013, at 14:16, Mark Petrovic <[email protected]> wrote: > [Originally posted on 12/26/2012, but it apparently did not make it to the > list archives. msp] > > Hi. Thank you for SLF4J and Logback. > > I have this line of code that just today came in from an upstream dependency > out of my control: > > private static final Logger logger = Logger.getLogger(FooImpl.class); > static { > logger.setLevel(Level.DEBUG); <<<<<<<<<<<<<<<< > } > > Unfortunately, this is logging code I had been successfully bridging, but > this setLevel() call on a Log4J logger breaks it. > > Do I have any elegant recourse beyond asking the developers of the line of > code to not do this? > > Thanks. > > -- > Mark > _______________________________________________ > Logback-user mailing list > [email protected] > http://mailman.qos.ch/mailman/listinfo/logback-user
_______________________________________________ Logback-user mailing list [email protected] http://mailman.qos.ch/mailman/listinfo/logback-user
