[jira] Resolved: (TRINIDAD-617) Fix MVariableResolver to use Calendar APIs instead of deprecated Date APIs

["Matthias Weßendorf (JIRA)" <de...@myfaces.apache.org>]

     [ https://issues.apache.org/jira/browse/TRINIDAD-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthias Weßendorf resolved TRINIDAD-617.
-----------------------------------------

    Resolution: Won't Fix

> Fix MVariableResolver to use Calendar APIs instead of deprecated Date APIs
> --------------------------------------------------------------------------
>
>                 Key: TRINIDAD-617
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-617
>             Project: MyFaces Trinidad
>          Issue Type: Test
>    Affects Versions: 1.0.1-incubating-core-SNAPSHOT
>            Reporter: Yee-Wah Lee
>            Priority: Trivial
>         Attachments: ChooseDateRenderer.patch, trinidad-impl.patch, trinidad-impl.patch
>
>
> MVariableResolver is used by the ChooseDateRenderer tests to get min, max and midDate values. This is so the tests always generate the same output. 
> However, the APIs used in the code are the deprecated Date constructors. I will replace them with the suggested GregorianCalendar equivalents.  
> Patch file contains changes to MVariableResolver.java (new Calendar calls, and some import cleanups) and the corresponding chooseDate golden files

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.