Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 41292 invoked from network); 8 Feb 2006 05:51:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 8 Feb 2006 05:51:12 -0000 Received: (qmail 63092 invoked by uid 500); 8 Feb 2006 05:51:10 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 63067 invoked by uid 500); 8 Feb 2006 05:51:09 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: 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 63055 invoked by uid 99); 8 Feb 2006 05:51:09 -0000 X-ASF-Spam-Status: No, hits=0.6 required=10.0 tests=NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Feb 2006 21:51:09 -0800 Received: by ajax.apache.org (Postfix, from userid 99) id DB2CFDE; Wed, 8 Feb 2006 06:50:47 +0100 (CET) From: bugzilla@apache.org To: commons-dev@jakarta.apache.org Subject: DO NOT REPLY [Bug 37484] - [logging] call to getClassLoader() in LogFactoryImpl not checked for null In-Reply-To: X-Bugzilla-Reason: AssignedTo Message-Id: <20060208055047.DB2CFDE@ajax.apache.org> Date: Wed, 8 Feb 2006 06:50:47 +0100 (CET) X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG� RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND� INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=37484 ------- Additional Comments From skitching@apache.org 2006-02-08 06:50 ------- Thanks for the info Luke. I would like to see JCL 1.1 be compatible with java 1.1, though it isn't a pre-requisite for the release. As Robert says, a statically-bound version should work. As soon as the 1.1 release is made, I'm keen to get started on a JCL 2.0 implementation that would use some kind of "static binding", ie one jar per implementation. In this case, there would be a simple non-TCCL-aware jar that you could use, and a separate TCCL-aware jar for people using servlet container style frameworks. However it isn't too difficult to just catch the NoSuchMethodError in this case. I've committed a change to do that (r375866), so if you could test by building from source, using a nightly build or the next release candidate that would be appreciated. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org