[
https://issues.apache.org/jira/browse/JDO-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665875#comment-13665875
]
Craig L Russell commented on JDO-720:
-------------------------------------
I applied the patch and ran the tck.
Only two reported problems:
*> Running tests for jdoql.conf with applicationidentity on 'derby' mapping=
... FAIL
*> Running tests for jdoql.conf with datastoreidentity on 'derby' mapping= ...
FAIL
But that didn't stop mvn from reporting success
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:47:37.429s
[INFO] Finished at: Fri May 17 09:31:59 PDT 2013
[INFO] Final Memory: 20M/460M
[INFO] ------------------------------------------------------------------------
I tried to find a log with the actual problem but could not find any error
indicators in the jdoql logs.
> Possible time zone issue in SupportedDateMethods
> ------------------------------------------------
>
> Key: JDO-720
> URL: https://issues.apache.org/jira/browse/JDO-720
> Project: JDO
> Issue Type: Bug
> Components: tck
> Affects Versions: JDO 3 update 1 (3.0.1)
> Reporter: Michael Bouschen
> Fix For: JDO 3 maintenance release 1 (3.1)
>
> Attachments: JDO-720.patch
>
>
> The TCK query test SupportedDateMethods fails when running a Date.getDate
> query: the query result is empty where it should include an employee
> instacne.
> Please note, the failure occurs when running the test in California and
> Arizona, but not in Europe.
> Looks like the problem is in the company model reader creating a date in the
> America/New_York time zone that is actually yesterday in other time zones, so
> the tests fail.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
