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 15CEFD470 for ; Tue, 25 Sep 2012 16:26:08 +0000 (UTC) Received: (qmail 94604 invoked by uid 500); 25 Sep 2012 16:26:07 -0000 Delivered-To: apmail-commons-issues-archive@commons.apache.org Received: (qmail 94527 invoked by uid 500); 25 Sep 2012 16:26:07 -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 94518 invoked by uid 99); 25 Sep 2012 16:26:07 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Sep 2012 16:26:07 +0000 Date: Wed, 26 Sep 2012 03:26:07 +1100 (NCT) From: "Sebb (JIRA)" To: issues@commons.apache.org Message-ID: <450476714.123160.1348590367737.JavaMail.jiratomcat@arcas> Subject: [jira] [Created] (LANG-828) FastDateParser does not handle non-Gregorian calendars properly MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Sebb created LANG-828: ------------------------- Summary: FastDateParser does not handle non-Gregorian calendars properly Key: LANG-828 URL: https://issues.apache.org/jira/browse/LANG-828 Project: Commons Lang Issue Type: Bug Components: lang.time.* Affects Versions: 3.1 Reporter: Sebb Assignee: Sebb The following calendars are non-Gregorian [1]: ja_JP_JP - Japanese Imperial) th_TH (with any variant) - Thai Buddhist This causes errors when testing round-trip conversions. The simplest solution is to fall back to SimpleDateFormat for these calendars. [1] http://docs.oracle.com/javase/6/docs/technotes/guides/intl/calendar.doc.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira