On 12/02/2010 1:17 PM, Drew Farris wrote:
Regardless, of these points, I can make the change locally, but I think that generally slf4j -> slf4j-jcl -> log4j is probably the right way to go.
Here are my unsolicited 2c. slf4j-jcl is merely an slf4j adapter for jcl. So, when the SLF4J API is invoked and the binding is slf4j-jcl, the complete flow is actually slf4j -> slf4j-jcl -> jcl -> log4j. SLF4J delegates to JCL which delegates to log4j. Instead of SLF4J delegating to JCL, you could have SLF4J *replace* JCL. Simply replace commons-logging.jar with jcl-over-slf4j.jar. See [1] for more info. BTW, you should consider logback [2] as an alternative to log4j. Cheers, [1] http://slf4j.org/legacy.html [2] http://logback.qos.ch -- Ceki
