Well, not the consensus I wanted. I have always wanted SLF4J to be the preferred logging _implementation_. My thin wrapper API would just delegate to it. So although we are now using SLF4J as I wanted, we haven't reached a consensus in eliminating _required_ 3rd party APIs entirely.
That's what I want most of all. If the end user doesn't include SLF4J jars in their classpath or commons logging jars, I wanted it to default automatically to the JDK 1.4 logging. If on 1.3, I wanted it to default to the console. Is that too much to ask for? ;) On Fri, Jul 11, 2008 at 3:59 PM, Emmanuel Lecharny <[EMAIL PROTECTED]> wrote: > Les Hazlewood wrote: >> >> I just completed this change and committed it. We now no longer have >> any dependencies on Commons Logging. >> > > AND we have reached a kind of consensus, the Apache way :) > > Thanks Les ! > > > -- > -- > cordialement, regards, > Emmanuel Lécharny > www.iktek.com > directory.apache.org > > >
