Return-Path: X-Original-To: apmail-commons-issues-archive@minotaur.apache.org Delivered-To: apmail-commons-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id ECD369609 for ; Tue, 27 Mar 2012 13:22:49 +0000 (UTC) Received: (qmail 60986 invoked by uid 500); 27 Mar 2012 13:22:49 -0000 Delivered-To: apmail-commons-issues-archive@commons.apache.org Received: (qmail 60917 invoked by uid 500); 27 Mar 2012 13:22:49 -0000 Mailing-List: contact issues-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: issues@commons.apache.org Delivered-To: mailing list issues@commons.apache.org Received: (qmail 60909 invoked by uid 99); 27 Mar 2012 13:22:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Mar 2012 13:22:49 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Mar 2012 13:22:48 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 2F6E7348C62 for ; Tue, 27 Mar 2012 13:22:27 +0000 (UTC) Date: Tue, 27 Mar 2012 13:22:27 +0000 (UTC) From: "Nicola Barbiero (Created) (JIRA)" To: issues@commons.apache.org Message-ID: <939223651.23118.1332854547637.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Created] (LANG-796) DateUtils.addDays does not work properly with daylight saving time (DST) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org DateUtils.addDays does not work properly with daylight saving time (DST) ------------------------------------------------------------------------ Key: LANG-796 URL: https://issues.apache.org/jira/browse/LANG-796 Project: Commons Lang Issue Type: Bug Components: lang.time.* Affects Versions: 2.6 Reporter: Nicola Barbiero DateUtils.addDays does not work properly with daylight saving time. The signature of the method is Date addDays(Date date, int amount) and the javadocs says "Adds a number of days to a date returning a new object. The original date object is unchanged", so if X=date.getTime() is the number of milliseconds of the date in input, the expected behaviour is that the returned Date has a number of milliseconds equal to X+amount*(86400000), where 86400000 is the number of milliseconds in one day. But when the calculation goes across the DST change date, the number of milliseconds added does not correspond to whole days. For example, here in Brussels, this code fragment: Date input = DateUtils.parseDateStrictly("25-03-2012_00:00", new String[] { "dd-MM-yyyy_HH:mm" }); Date output = DateUtils.addDays(input, 1); will give: 'input' equals to "Sun Mar 25 00:00:00 CET 2012" ==> input.getTime() equals to 1332630000000 'output' equals to "Mon Mar 26 00:00:00 CEST 2012" ==> output.getTime() equals to 1332712800000 where 1332712800000-1332630000000=82800000 < 86400000 (in fact 82800000 is equivalent to 23h). Since addDays is working with objects Date, it should not be influenced by events like the DST. Proposed solution: replace the current implementation public static Date add(Date date, int calendarField, int amount) { if (date == null) { throw new IllegalArgumentException("The date must not be null"); } Calendar c = Calendar.getInstance(); c.setTime(date); c.add(calendarField, amount); return c.getTime(); } based on Calendar with an implementation that works only with Date objects, for example: public static Date add(Date date, int calendarField, int amount) { if (date == null) { throw new IllegalArgumentException("The date must not be null"); } return new Date(input.getTime() + amount * 86400000l); } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira