Hi Robert, I modified the javadocs for SLF4JBridgeHandler Programmatic installation: // Optionally remove existing handlers attached to j.u.l root logger SLF4JBridgeHandler.removeHandlersForRootLogger(); // (since SLF4J 1.6.5) // add SLF4JBridgeHandler to j.u.l's root logger, should be done once // during the initialization phase of your application SLF4JBridgeHandler.install(); Installation via logging.properties configuration file: // register SLF4JBridgeHandler as handler for the j.u.l. root logger handlers = org.slf4j.bridge.SLF4JBridgeHandler Your comments welcome. By the way, the javadocs for SLF4JBridgeHandler state that"essentially, the idea is to install on the root logger an instance of SLF4JBridgeHandler as the sole JUL handler in the system." I think the word "sole" goes a little over board. If the user wishes to use other handlers, they are welcome to do so. (We have no mandate to tacitly override jul config.) -- Ceki http://twitter.com/#!/ceki On 08.05.2012 13:55, ceki wrote:
Hi Robert,
I had not considered overwriting the logging.properties file. It's a great idea. I'll document it shortly. Having said that, including logging.properties in jul-to-slf4j.jar would be an indefensible case of "do as say not as i do" [1]. Our credibility aside, does jul-to-slf4j.jar have the mandate to override j.u.l. configuration? I don't think jul-to-slf4j.jar has any such mandate...
Cheers,