From dev-return-61189-apmail-ant-dev-archive=ant.apache.org@ant.apache.org Fri Oct 29 05:47:53 2004 Return-Path: Delivered-To: apmail-ant-dev-archive@www.apache.org Received: (qmail 97975 invoked from network); 29 Oct 2004 05:47:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 29 Oct 2004 05:47:53 -0000 Received: (qmail 27592 invoked by uid 500); 29 Oct 2004 05:47:09 -0000 Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 27514 invoked by uid 500); 29 Oct 2004 05:47:08 -0000 Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list dev@ant.apache.org Received: (qmail 27494 invoked by uid 99); 29 Oct 2004 05:47:08 -0000 X-ASF-Spam-Status: No, hits=1.5 required=10.0 tests=DNS_FROM_RFC_POST X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from [24.93.47.44] (HELO ms-smtp-05-eri0.texas.rr.com) (24.93.47.44) by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 28 Oct 2004 22:47:06 -0700 Received: from [192.168.10.100] (cs242764-74.houston.rr.com [24.27.64.74]) by ms-smtp-05-eri0.texas.rr.com (8.12.10/8.12.7) with ESMTP id i9T5l0Pa018460 for ; Fri, 29 Oct 2004 00:47:00 -0500 (CDT) Mime-Version: 1.0 (Apple Message framework v619) In-Reply-To: <4181D01A.4040707@apache.org> References: <4181D01A.4040707@apache.org> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Curt Arnold Subject: Re: [human-assisted gump] log4j back incompatible change Date: Fri, 29 Oct 2004 00:46:59 -0500 To: Ant Developers List X-Mailer: Apple Mail (2.619) X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N I took a quick look at the break and in no way can speak for log4j or Ceki, but thought I would give a quick analysis to show how little I know of the problem. On Oct 29, 2004, at 12:07 AM, Stefano Mazzocchi wrote: > > 1) if you might be willing to revert the change if you did not intend > to cause such effect > Swapping the derivation from Category extends Logger from Logger extends Category has been long expected and surely intentional. Catgegory has long been deprecated and this was a move to finally eliminate it from the tree. At least one of the breaks occurred since the return type of Category.getLogger changed from Category to Logger with the swap. To retain compatibility with old code, it would appear that Category would have to encapsulate Logger instead of extending it. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional commands, e-mail: dev-help@ant.apache.org