ds,
Ramanand.
-Original Message-
From: Stephen Colebourne [mailto:scolebou...@joda.org]
Sent: Wednesday, December 09, 2015 4:46 PM
To: core-libs-dev
Cc: i18n-dev
Subject: Re: Review request for JDK-8066982:
ZonedDateTime.parse() returns wrong ZoneOffset around DST fall transition
The logi
this patch which were proposed in
>>> the bug.
>>>
>>> Bug link is: https://bugs.openjdk.java.net/browse/JDK-8066982
>>>
>>>
>>> Regards,
>>> Ramanand.
>>>
>>>
>>> -Original Message-
>>> From:
penjdk.java.net
> Cc: HYPERLINK "mailto:i18n-...@openjdk.java.net; i18n-...@openjdk.java.net
> Subject: Re: Review request for JDK-8066982: ZonedDateTime.parse()
> returns wrong ZoneOffset around DST fall transition
>
> Hi,
>
> Stephen, can you confirm that the added text an
-...@openjdk.java.net
Subject: Re: Review request for JDK-8066982: ZonedDateTime.parse()
returns wrong ZoneOffset around DST fall transition
Hi Ramanand,
Thanks for the cleanup of the test.
On 12/14/2015 3:14 AM, Ramanand Patil wrote:
Hi Roger and all,
Please review the updated Webrev:
http
Hi Ramanand,
Thanks for the cleanup of the test.
On 12/14/2015 3:14 AM, Ramanand Patil wrote:
RE: Review request for JDK-8066982: ZonedDateTime.parse()
returns wrong ZoneOffset around DST fall transition
Hi Rogerand all,
Please review the updated
Webrev:_http://cr.openjdk.java.net/~ntv
e modified the fix and test cases as per inputs given by Stephen.
>>> Also, I have added the javadocs changes in this patch which were proposed in
>>> the bug.
>>>
>>> Bug link is: https://bugs.openjdk.java.net/browse/JDK-8066982
>>>
>>>
>>
ailto:i18n-...@openjdk.java.net; i18n-...@openjdk.java.net
Subject: Re: Review request for JDK-8066982: ZonedDateTime.parse()
returns wrong ZoneOffset around DST fall transition
Hi,
Stephen, can you confirm that the added text and test in DateTimeFormatter is
not a specification change?
Our proc
066982: ZonedDateTime.parse()
returns wrong ZoneOffset around DST fall transition
The logic looks fine.
In the main code, this part
.getLong(INSTANT_SECONDS);
can be replaced with
.toEpochSecond();
which will be slightly faster.
In the test case, this part
.plus(15, ChronoUnit.MINUTES
-Original Message-
> From: Stephen Colebourne [mailto:scolebou...@joda.org]
> Sent: Wednesday, December 09, 2015 4:46 PM
> To: core-libs-dev
> Cc: i18n-dev
> Subject: Re: Review request for JDK-8066982: ZonedDateTime.parse()
> returns wrong ZoneOffset around DST fall transitio
://bugs.openjdk.java.net/browse/JDK-8066982
Regards,
Ramanand.
-Original Message-
From: Stephen Colebourne [mailto:scolebou...@joda.org]
Sent: Wednesday, December 09, 2015 4:46 PM
To: core-libs-dev
Cc: i18n-dev
Subject: Re: Review request for JDK-8066982: ZonedDateTime.parse()
returns wrong ZoneOffset
The logic looks fine.
In the main code, this part
.getLong(INSTANT_SECONDS);
can be replaced with
.toEpochSecond();
which will be slightly faster.
In the test case, this part
.plus(15, ChronoUnit.MINUTES);
can be replaced with
.plusMinutes(15)
And
.with(ChronoField.OFFSET_SECONDS,
HI all,
Please review a fix for Bug - HYPERLINK
"https://bugs.openjdk.java.net/browse/JDK-8066982"JDK-8066982
Bug - Parsing a string with ZonedDateTime.parse() that contains zone offset and
zone ID "Europe/Berlin" returns a wrong ZonedDateAndTime (different offset).
This error starts
12 matches
Mail list logo
