You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2015/06/18 22:43:01 UTC

[jira] [Commented] (LANG-1002) Several predefined ISO FastDateFormats in DateFormatUtils are incorrect

    [ https://issues.apache.org/jira/browse/LANG-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14592477#comment-14592477 ] 

Michael Osipov commented on LANG-1002:
--------------------------------------

[~garydgregory], it has been already more than a year. I'd like to finalize this issue now. Please read my previous comment.
I'd like to remove all invalid static patterns in 4.0 and deprecate them in 3.x.

> Several predefined ISO FastDateFormats in DateFormatUtils are incorrect
> -----------------------------------------------------------------------
>
>                 Key: LANG-1002
>                 URL: https://issues.apache.org/jira/browse/LANG-1002
>             Project: Commons Lang
>          Issue Type: Bug
>          Components: lang.time.*
>    Affects Versions: 3.3.2
>            Reporter: Michael Osipov
>
> Formats {{ISO_TIME_FORMAT}}, {{ISO_TIME_TIME_ZONE_FORMAT}} prepend a {{T}} but this is not correct. Sole time is never prepended by defintion. {{T}} is used only when date *and* time are given.
> The Javadocs of {{ISO_TIME_NO_T_FORMAT}}, {{ISO_TIME_NO_T_FORMAT}} are in correct too because they say: "This pattern does not comply with the formal ISO8601 specification as the standard requires the 'T' prefix for times."
> You might want to read [Markus Kuhn's reference|https://www.cl.cam.ac.uk/~mgk25/iso-time.html#time] on that.
> A solution would be remove the first two and rename the second two by dropping the {{NO_T}} in the name.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)