On 10/28/05, Remy Maucherat <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > Author: costin > > Date: Thu Oct 27 19:55:08 2005 > > New Revision: 329053 > > > > URL: http://svn.apache.org/viewcvs?rev=329053&view=rev > > Log: > > Implementation of commons-logging that doesn't use any discovery or > > tricks, just plain java.util.logging. > > > > There is a trick actually - at startup it'll try to load a different > > handler ( without 2-lines logs ) and a different config ( from classpath > > like log4j ). I'll probably remove this later, but I can't stand the > > default handler and behavior > > I'm ok with including your formatter in the JULI bundle, and using it in > the default configuration (the one which is in conf/logging.properties).
I've been wondering - was is the reason for having JULI as a separate module ? It would fit well under util/. If JDK1.4 is the concern - exclude is pretty easy, there are other files depending on 1.4 or even 1.5 in the tree. Costin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
