You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@causeway.apache.org by "Andi Huber (Jira)" <ji...@apache.org> on 2025/04/03 07:41:00 UTC
[jira] [Closed] (CAUSEWAY-3880) [Testing] JavaSqlDateValueSemanticsProviderTest potentially fails with expected: <1970-01-01> but was: <1969-12-31>
[ https://issues.apache.org/jira/browse/CAUSEWAY-3880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andi Huber closed CAUSEWAY-3880.
--------------------------------
> [Testing] JavaSqlDateValueSemanticsProviderTest potentially fails with expected: <1970-01-01> but was: <1969-12-31>
> -------------------------------------------------------------------------------------------------------------------
>
> Key: CAUSEWAY-3880
> URL: https://issues.apache.org/jira/browse/CAUSEWAY-3880
> Project: Causeway
> Issue Type: Bug
> Components: Core
> Reporter: Andi Huber
> Assignee: Andi Huber
> Priority: Major
> Fix For: 3.3.0
>
>
> Test is sensitive to the system's default timezone.
> The implied assumption, that
>
> {code:java}
> new java.sql.Date(0L).toString(){code}
>
> always produces '1970-01-01' does not hold e.g. when using
> {code:java}
> TimeZone.setDefault(TimeZone.getTimeZone("GMT-8")){code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)