You are viewing a plain text version of this content. The canonical link for it is here.
Posted to adffaces-issues@incubator.apache.org by "Matthias Weßendorf (JIRA)" <ad...@incubator.apache.org> on 2007/03/16 08:41:20 UTC
[jira] Updated: (ADFFACES-316) Fix MVariableResolver to use
Calendar APIs instead of deprecated Date APIs
[ https://issues.apache.org/jira/browse/ADFFACES-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthias Weßendorf updated ADFFACES-316:
----------------------------------------
Affects Version/s: 1.0.1-incubating-core-SNAPSHOT
> Fix MVariableResolver to use Calendar APIs instead of deprecated Date APIs
> --------------------------------------------------------------------------
>
> Key: ADFFACES-316
> URL: https://issues.apache.org/jira/browse/ADFFACES-316
> Project: MyFaces ADF-Faces
> 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.