commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulo Gaspar" <paulo.gas...@krankikom.de>
Subject RE: [Logging] [VOTE] Commons Logging 1.0 Release
Date Wed, 30 Jan 2002 12:21:31 GMT
Hi Geir,


Knowing both code bases I would say that Avalon is better in 1) but
as nothing in 2).

For my logging wrapper I am using Avalon stuff for the wrappers and
Velocity stuff as a base for detection and configuration... and for
the Primordial Logger, which no one is talking about but that I find
a great idea.


Have fun,
Paulo Gaspar

> -----Original Message-----
> From: Geir Magnusson Jr. [mailto:geirm@optonline.net]
> Sent: Wednesday, January 30, 2002 12:56 PM
> To: Jakarta Commons Developers List
> Subject: Re: [Logging] [VOTE] Commons Logging 1.0 Release
> 
> ...
> 
> Just to throw another log on the fire...
> 
> We did too in Velocity-land, and built the following, a while ago :
> 
> 1) Simple interface through which Velocity would happily log into any
> supplied class/object that supported that interface.
> 
> 2) 'Autodetection' - when the user didn't specify the logsystem they
> preferred, we would look for log4j or logkit in the classpath, and use
> whatever we found.  That means that you can just put the log4j.jar or
> logkit.jar into the classpath, and velocity will automatically 
> log to a file
> using that system.
> 
> My point?  I don't know - just noting that there are others in 
> jakarta-land
> with similar problems and solutions (like Paulo...)
> 
> 
> -- 
> Geir Magnusson Jr.                       geirm@optonline.net
> System and Software Consulting
> You're going to end up getting pissed at your software
> anyway, so you might as well not pay for it. Try Open Source.


--
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