I forgot to also mention this page which explains how to have all external fwks log to SLF4J: http://www.slf4j.org/legacy.html 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...

* 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

On 05/09/2011 01: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...

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

+1. -- Sergiu Dumitriu http://purl.org/net/sergiu/

+1 Thanks, Marius On 05/09/2011 02: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...

* 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

There's one issue with slf4j to be aware of. As you probably know slf4j does not allow several versions of slf4j (APIs and implementations) to be located in the classpath. This applies for e.g. JBoss 5.1. It internally uses older version of slf4j. By default in JBoss 5.1 applications do not have isolated classpath. This results in JBoss slf4j being loaded first and potentially conflicting with your app's slf4j may you try to deploy (especially for newer versions of slf4j). This may not be a critical issue (in our case things worked, but we've isolated our web application's classpath and yet the warning got printed), but worth double-checking. Check this post for the details of the issue http://community.jboss.org/thread/157454 Regards, Roman -- View this message in context: http://xwiki.475771.n2.nabble.com/Proposal-Switch-from-Commons-Logging-Log4j... Sent from the XWiki- Dev mailing list archive at Nabble.com.