Also note that this doesn't change our component code since they use our Logging Facade and are thus isolated.
Thanks -Vincent On May 9, 2011, at 1:37 PM, Vincent Massol wrote: > Hi, > > I'd like to propose switching from Commons Logging/Log4j to SLF4J/Logback for > the following reasons: > > * slf4j was written to solve the issues with commons logging (memory leaks > under some circumstances). > http://www.google.fr/search?aq=f&sourceid=chrome&ie=UTF-8&q=slf4j+vs+commons+logging > > * logback is the successor of log4j and addresses the following when compared > to lgog4j: > http://logback.qos.ch/reasonsToSwitch.html > > * New stuff happens in logback and not in log4j > > * I'd also like to switch to logback since it has full-fledged JMX support > which allows us to easily change logging configuration at runtime (changing > log levels for example): > http://logback.qos.ch/manual/jmxConfig.html > > Note that migrating a log4j.properties file is easy: > http://logback.qos.ch/translator/ > > In addition if a user wants to stay on log4j it would be possible and easy: > simply remove the logback jar and replace it with the slf4j-log4j one. > > WDYT? > > Thanks > -Vincent _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
