Return-Path: Delivered-To: apmail-logging-log4j-dev-archive@www.apache.org Received: (qmail 35969 invoked from network); 24 Jul 2006 08:52:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 24 Jul 2006 08:52:36 -0000 Received: (qmail 99314 invoked by uid 500); 24 Jul 2006 08:52:36 -0000 Delivered-To: apmail-logging-log4j-dev-archive@logging.apache.org Received: (qmail 99028 invoked by uid 500); 24 Jul 2006 08:52:35 -0000 Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Log4J Developers List" Reply-To: "Log4J Developers List" Delivered-To: mailing list log4j-dev@logging.apache.org Received: (qmail 99017 invoked by uid 99); 24 Jul 2006 08:52:35 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Jul 2006 01:52:35 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [151.193.220.17] (HELO sgtulmg01-out.sabre.com) (151.193.220.17) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Jul 2006 01:52:34 -0700 Received: from unknown (HELO sglonmg02-out.sabre.com) ([10.136.87.24]) by sgtulmg01-out.sabre.com with ESMTP; 24 Jul 2006 03:52:13 -0500 X-ExtLoop2: From 10.136.87.24 X-BypassContentFilters: true X-IronPort-AV: i="4.07,174,1151902800"; d="scan'208"; a="884840050:sNHT116709452" Received: from unknown (HELO sglonbh01.Global.ad.sabre.com) ([10.136.85.54]) by sglonmg02-out.sabre.com with ESMTP; 24 Jul 2006 09:51:54 +0100 X-ExtLoop1: From 10.136.85.54 X-IronPort-AV: i="4.07,174,1151881200"; d="scan'208"; a="4553909:sNHT33973541" Received: from sglonms01.Global.ad.sabre.com ([10.136.85.17]) by sglonbh01.Global.ad.sabre.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 24 Jul 2006 09:51:53 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: Daily/Rolling appenders compatibility issue Date: Mon, 24 Jul 2006 09:51:54 +0100 Message-ID: <22B03FEE1AD88845B4AEF75D0461F2229D3678@sglonms01.Global.ad.sabre.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Daily/Rolling appenders compatibility issue Thread-Index: Acau4mFTNyEaDLvQRIae9jR/3KaOKgAGzrWg From: "Karczmarczyk, Krzysztof" To: "Log4J Developers List" X-OriginalArrivalTime: 24 Jul 2006 08:51:53.0704 (UTC) FILETIME=[693B0680:01C6AEFE] X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi, Recent alpha release tried to remove daily/rolling file appenders incompatibilities for old config files. There is at least one remaining problem in this area: org.apache.log4j.DailyRollingFileAppender and org.apache.log4j.RollingFileAppender both implement Appender instead of extending from AppenderSkeleton. This removes threshold property from above appenders and breaks our work :). Could you please include this fix in your release plans for alpha 9? Regards, Kris --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org For additional commands, e-mail: log4j-dev-help@logging.apache.org