You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Chen (Jira)" <ji...@apache.org> on 2019/09/05 03:49:00 UTC

[jira] [Commented] (LANG-1462) After version Commons-lang3.4 DateFormatUtils has a bug

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

Chen commented on LANG-1462:
----------------------------

The TimeZone parameter of the format method is used to create an instance of FastDateFormat with an empty default value, so I don't think this is a BUG.

Just need to modify the method description.

> After version Commons-lang3.4 DateFormatUtils has a bug
> -------------------------------------------------------
>
>                 Key: LANG-1462
>                 URL: https://issues.apache.org/jira/browse/LANG-1462
>             Project: Commons Lang
>          Issue Type: Bug
>          Components: lang.time.*
>    Affects Versions: 3.5, 3.6, 3.7, 3.8, 3.9, 3.8.1
>            Reporter: Lijun Liang
>            Priority: Critical
>
> The code is as follows :
> Calendar cale = Calendar.getInstance();
>  System.out.println("Old time is " + DateFormatUtils.format(cale, "yyyyMMddHHmmss"));
>  cale.setTimeZone(TimeZone.getTimeZone("JST"));
>  System.out.println("New time is " + DateFormatUtils.format(cale, "yyyyMMddHHmmss"));
>  
> The results of commons-lang3 3.4:
> Old time is 20190605144536
> New time is 20190605154536
>  
> The results of the version after commons-lang3 3.4:
> Old time is 20190605144536
> New time is 20190605144536
>  
> We found that the time zone setting was invalidated when it was formatted
>  



--
This message was sent by Atlassian Jira
(v8.3.2#803003)