Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 4083 invoked from network); 1 Mar 2004 02:35:45 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 1 Mar 2004 02:35:45 -0000 Received: (qmail 47695 invoked by uid 500); 1 Mar 2004 02:35:24 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 47641 invoked by uid 500); 1 Mar 2004 02:35:24 -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 47626 invoked from network); 1 Mar 2004 02:35:24 -0000 Received: from unknown (HELO perpetua.mcclan.net) (208.161.106.6) by daedalus.apache.org with SMTP; 1 Mar 2004 02:35:24 -0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by perpetua.mcclan.net (8.12.8/8.12.8) with ESMTP id i212ZWKX011124 for ; Sun, 29 Feb 2004 18:35:33 -0800 Received: from localhost (localhost [127.0.0.1]) by localhost (IMP) with HTTP for ; Sun, 29 Feb 2004 18:35:32 -0800 Message-ID: <1078108532.4042a174e1447@localhost> Date: Sun, 29 Feb 2004 18:35:32 -0800 From: "Craig R. McClanahan" To: Jakarta Commons Developers List Subject: Re: [logging] Current Status and Release Planning References: <1078010872.404123f8592d4@localhost> <4041DDDC.9040000@mdh.se> In-Reply-To: <4041DDDC.9040000@mdh.se> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.2 X-Originating-IP: 127.0.0.1 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Quoting Dennis Lundberg : > I've been diffing the 1.0.3 release and the nightly from 20040229. I > thought that I would try the Lumberjack logging, but I can't see how it > could possibly work. It would work if you also provided a JSR-47 compliant implementation of the java.util.logging API classes that leveraged this underlying logging implementation, as Lumberjack was originally reported to include. > Here's a code snippet from LogFactoryImpl: > > /** > * Is JDK 1.3 with Lumberjack logging available? > */ > protected boolean isJdk13LumberjackAvailable() { > try { > loadClass("java.util.logging.Logger"); > loadClass("org.apache.commons.logging.impl.Jdk13LumberjackLogger"); > return (true); > } catch (Throwable t) { > return (false); > } > } > > In a pre 1.4 environment the line > loadClass("java.util.logging.Logger"); > is going to throw an exception, isn't it? I mean all the Lumberjack > classes are in the com.redstarhacker.lumberjack package. > > > On another note the version-numbers in build.xml and project.xml should > be changed to 1.0.4 before the release. > They will be - thanks for the reminder. > -- > Dennis Lundberg > Craig --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org