[
https://issues.apache.org/jira/browse/LANG-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16914775#comment-16914775
]
xia0c commented on LANG-1465:
-----------------------------
Thanks for confirming our bug and initiating a pull request. Sorry to see that
the pull request got rejected. Here are our suggestions: It doesn't need to
modify the basic ISO_8601 strategy. We could add a separate case to handle the
time format ending with ZZ.
> DateUtils.parseDate backward Incompatibility bug
> ------------------------------------------------
>
> Key: LANG-1465
> URL: https://issues.apache.org/jira/browse/LANG-1465
> Project: Commons Lang
> Issue Type: Bug
> Components: lang.time.*
> Affects Versions: 3.5, 3.6, 3.7, 3.8, 3.9, 3.8.1
> Environment: System: Linux testinglab 4.4.0-131-generic
> #157~14.04.1-Ubuntu
> Java version "1.8.0_191"
> Java(TM) SE Runtime Environment (build 1.8.0_191-b12)
> Java HotSpot(TM) 64-Bit Server VM (build 25.191-b12, mixed mode)
>
>
> Reporter: xia0c
> Priority: Major
> Labels: performance
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Hi,
> The following code snippets throw a ParseException when trying to parse the
> time. It works well before commons-lang 3.4. When I update commons-lang to
> 3.5 or newer versions, it failed.
> {code:java}
> @Test
> public void Demo() throws ParseException {
> assertEquals("Tue Jun 11 15:06:11 CDT 2019",
> DateUtils.parseDate("2019-06-11T15:06:11.716-0500",
> "yyyy-MM-dd'T'HH:mm:ss.SSSZZ"));
>
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
