commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Sanders" <ssand...@nextance.com>
Subject RE: cvs commit: jakarta-commons/logging/src/java/org/apache/commons/loggingJdk14Logger.java LogSource.java package.html
Date Mon, 07 Jan 2002 23:16:50 GMT
Alright, you got me there.  I just didn't like it complaining about it
:)

> -----Original Message-----
> From: Morgan Delagrange [mailto:mdelagra@yahoo.com] 
> Sent: Monday, January 07, 2002 3:19 PM
> To: Jakarta Commons Developers List
> Subject: Re: cvs commit: 
> jakarta-commons/logging/src/java/org/apache/commons/loggingJdk
> 14Logger.java LogSource.java package.html
> 
> 
> Well, that's a default config of sorts.  :)  If you do not 
> have a log4j.properties file in your classpath, Log4j uses a 
> no-op logger.
> 
> ----- Original Message -----
> From: "Scott Sanders" <ssanders@nextance.com>
> To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
> Sent: Monday, January 07, 2002 2:09 PM
> Subject: RE: cvs commit: 
> jakarta-commons/logging/src/java/org/apache/commons/loggingJdk
> 14Logger.java
> LogSource.java package.html
> 
> 
> I am just thinking back to the last time that I used Log4J 
> without initializing it.  It complains.  I will look into it 
> and report back.  I agree in general that Log4J should have 
> some default config.
> 
> Scott
> 
> > -----Original Message-----
> > From: Craig R. McClanahan [mailto:craigmcc@apache.org]
> > Sent: Monday, January 07, 2002 12:09 PM
> > To: Jakarta Commons Developers List
> > Subject: RE: cvs commit: 
> > jakarta-commons/logging/src/java/org/apache/commons/loggingJdk
> > 14Logger.java LogSource.java package.html
> >
> >
> >
> >
> > On Mon, 7 Jan 2002, Scott Sanders wrote:
> >
> > > Date: Mon, 7 Jan 2002 11:20:41 -0800
> > > From: Scott Sanders <ssanders@nextance.com>
> > > Reply-To: Jakarta Commons Developers List 
> > > <commons-dev@jakarta.apache.org>
> > > To: Jakarta Commons Developers List 
> <commons-dev@jakarta.apache.org>
> > > Subject: RE: cvs commit:
> > >     jakarta-commons/logging/src/java/org/apache/commons/logging
> > >     Jdk14Logger.java LogSource.java package.html
> > >
> > > Do we need something more than just checking for the class
> > in Log4J.
> > > Isn't there some way to see if it has been configured?
> > Wouldn't that
> > > be better?
> > >
> >
> > Not necessarily.
> >
> > Doesn't Log4J have a default configuration?  (If it doesn't, it 
> > should).
> >
> > If the application doesn't want to use Log4J for logging, 
> it shouldn't 
> > be on the classpath at all.  On the other hand, if the 
> classes *are* 
> > there, then the configuration file should have been put in 
> the right 
> > place also.
> >
> > Trying to build logging-package-specific knowledge like this into a 
> > "thin" wrapper layer seems like a slippery slope.
> >
> > > Scott
> >
> > Craig
> >
> >
> > --
> > To unsubscribe, e-mail:
> > <mailto:commons-dev-> unsubscribe@jakarta.apache.org>
> > For
> > additional commands,
> > e-mail: <mailto:commons-dev-help@jakarta.apache.org>
> >
> >
> 
> --
> To unsubscribe, e-mail: 
> <mailto:commons-dev-> unsubscribe@jakarta.apache.org>
> For 
> additional commands, 
> e-mail: <mailto:commons-dev-help@jakarta.apache.org>
> 
> 
> 
> _________________________________________________________
> 
> Do You Yahoo!?
> 
> Get your free @yahoo.com address at http://mail.yahoo.com
> 
> 
> 
> 
> --
> To unsubscribe, e-mail:   
> <mailto:commons-dev-> unsubscribe@jakarta.apache.org>
> For 
> additional commands, 
> e-mail: <mailto:commons-dev-help@jakarta.apache.org>
> 
> 

--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message