You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Pascal Schumacher (JIRA)" <ji...@apache.org> on 2015/06/11 19:15:00 UTC
[jira] [Resolved] (GROOVY-7462) groovy.json.internal.Dates
instantiates objects without explicitly specifying the miliseconds
parameter
[ https://issues.apache.org/jira/browse/GROOVY-7462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pascal Schumacher resolved GROOVY-7462.
---------------------------------------
Resolution: Fixed
Fix Version/s: 2.5.0-beta-1
2.4.4
Assignee: Pascal Schumacher (was: Guillaume Laforge)
> groovy.json.internal.Dates instantiates objects without explicitly specifying the miliseconds parameter
> -------------------------------------------------------------------------------------------------------
>
> Key: GROOVY-7462
> URL: https://issues.apache.org/jira/browse/GROOVY-7462
> Project: Groovy
> Issue Type: Bug
> Components: JSON
> Affects Versions: 2.4.3
> Reporter: Pascal Schumacher
> Assignee: Pascal Schumacher
> Fix For: 2.4.4, 2.5.0-beta-1
>
>
> groovy.json.internal.Dates instantiates objects without explicitly specifying the miliseconds parameter. By omission, it ends up using the value provided by Calendar.getInstance(), which is copied over from System.currentTimeMillis(). This is a problem when comparing dates.
> Source: [https://mail-archives.apache.org/mod_mbox/incubator-groovy-dev/201506.mbox/%3CCAJ_y_NCp4EKX11DCd%3D%3D7pkoS-16Y2JBnB6xpy%2BDQenYTaOV9Ew%40mail.gmail.com%3E]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)