[
https://issues.apache.org/jira/browse/LANG-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15873988#comment-15873988
]
Charles Honton commented on LANG-1305:
--------------------------------------
If you need the colon in the input, then use the 'X' format specifier. Without
the colon, use the 'z' or 'Z' format specifier. The fact that a prior version
of FastDateFormat would accept the colon was a bug.
> FastDateFormat in 3.5 failed test of 3.3.2 while parsing
> 2014-12-15T19:50:00-05:00
> ----------------------------------------------------------------------------------
>
> Key: LANG-1305
> URL: https://issues.apache.org/jira/browse/LANG-1305
> Project: Commons Lang
> Issue Type: Bug
> Components: lang.time.*
> Affects Versions: 3.5
> Environment: Windows7, JDK1.8U112
> Reporter: Nathanael Yang
>
> FastDateFormat.getInstance("yyyy-MM-dd'T'HH:mm:ssZ",
> TimeZone.getTimeZone("GMT-05:00")).parse("2014-12-15T19:50:00-05:00");
> This will work on 3.3.2, however, when I upgraded to 3.5 it failed like this:
> Exception in thread "main" java.text.ParseException: Unparseable date:
> 2014-12-15T19:50:00-05:00
> This made me suprized and I have to carefully check my unit tests to see
> whether upgrade to 3.5 is reliable.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
