Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 9415 invoked from network); 10 Nov 2004 16:10:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 10 Nov 2004 16:10:09 -0000 Received: (qmail 67725 invoked by uid 500); 10 Nov 2004 16:09:49 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 67566 invoked by uid 500); 10 Nov 2004 16:09:45 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 67524 invoked by uid 99); 10 Nov 2004 16:09:40 -0000 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=NO_REAL_NAME,UPPERCASE_25_50 X-Spam-Check-By: apache.org Received: from [192.18.33.10] (HELO exchange.sun.com) (192.18.33.10) by apache.org (qpsmtpd/0.28) with SMTP; Wed, 10 Nov 2004 08:09:39 -0800 Received: (qmail 21187 invoked by uid 50); 10 Nov 2004 16:09:37 -0000 Date: 10 Nov 2004 16:09:37 -0000 Message-ID: <20041110160937.21186.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: dev@cocoon.apache.org Cc: Subject: DO NOT REPLY [Bug 30372] - The daylight time cause error when timezone is CST X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.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=30372 The daylight time cause error when timezone is CST ------- Additional Comments From vgritsenko@apache.org 2004-11-10 16:09 ------- I'm in favour of: > 2. Revert the jar and live with the bug in 2.1.x. Because this bug was already present in 2.1.5, it can live in 2.1.6 as well. Those who need this bug fixed can easily upgrade this library on their own. We should do our best to provide JDK1.3 support at this moment, and after 2.1.6 we can discuss option of dropping it. Vadim