Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 22658 invoked from network); 8 Jan 2002 05:23:18 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 8 Jan 2002 05:23:18 -0000 Received: (qmail 2043 invoked by uid 97); 8 Jan 2002 03:34:04 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 2027 invoked by uid 97); 8 Jan 2002 03:34:04 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 2015 invoked from network); 8 Jan 2002 03:34:03 -0000 Date: Mon, 07 Jan 2002 22:32:53 -0500 From: "Geir Magnusson Jr." Subject: Re: cvs commit: jakarta-commons/logging/src/java/org/apache/commons/logging Jdk14Logger.java LogSource.java package.html In-reply-to: To: Jakarta Commons Developers List Message-id: MIME-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT User-Agent: Microsoft-Entourage/10.0.0.1309 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On 1/7/02 8:38 PM, "Paulo Gaspar" wrote: >> Trying to build logging-package-specific knowledge like this into a "thin" >> wrapper layer seems like a slippery slope. > > For simple file based logging configuration it is actually quite simple > to do that for the 3 logging APIs we have been talking about. Very light. > > You can have a several modes: > - Give me some already configured logger (minimal common logging code): > - Find some logger already configured (just a bit more code); > - Configure the logger you find to log to this file (just a bit more); > > - Primordial logger and silly simple logger would take more than the > previous 2 bits. > > You can find some "log to this file" configuration code in Velocity for > both Log4J and LogKit. You can find it at: > CVS Repository: > jakarta-velocity > path: > \src\java\org\apache\velocity\runtime\log > I have been wanting to jump into this thread and mention it, but I am so hopelessly behind I can never seem to catch up. (Maybe I should stop yammering on general@) Yes, this system seems to work well for us, basically finding the first supported logging system in the classpath if no logger is configured by the application. -- 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: For additional commands, e-mail: