On Fri, May 23, 2008 at 11:41 AM, Felix Meschberger <[EMAIL PROTECTED]> wrote: > Am Freitag, den 23.05.2008, 11:35 +0200 schrieb Niklas Gustavsson: >> I would also add that the static fields might actually be used by >> clients who want to configure the JCL behavior. > > Well, as far as I can tell, jcl-over-slf4j ignores any JCL > configuration, because it is hardly linked to SLF4J. So any users of the > JCL LogFactory class out of the Sling log bundle, will always get SLF4J > backed JCL loggers no matter what they configure. > > Of course, their applications would break if they would use the > constants regardless of their use in here...
Right, that's pretty much the problem :-) >> > If it is for the first reason, we may "hack" this by just exporting the >> > o.a.commons.logging package as being of version 1.1.1. If for the second >> > reason, we can probably not do much about it. >> >> One possibility is to get SLF4J to support JCL 1.1.1, no idea if Ceki >> thinks that a worthwhile thing to do. > > I assume technically, it is not much: just update the dependency and > include the most recent LogFactory class. I don't know if he follows this list so I'll ask on the SLF4J list as well. /niklas
