Hi,
A release note would be a good idea to explain the change in behavior of
SMART mode,
I added label "release-note=yes"
Regards, Roger
On 05/30/2019 09:50 AM, Roger Riggs wrote:
Hi,
The behavior is within the spec and seems more just like a bug in the
implementation.
Also, an exception was thrown but it was for the wrong reason.
$.02, Roger
On 05/29/2019 06:55 PM, naoto.s...@oracle.com wrote:
Hi Joe,
Right, I will file a corresponding CSR.
Naoto
On 5/29/19 3:51 PM, Joseph D. Darcy wrote:
Hi Naoto,
Should this bug get a CSR for the behavioral change?
Cheers,
-Joe
On 5/29/2019 2:12 PM, naoto.s...@oracle.com wrote:
Hi,
Please review the fix for the following issue:
https://bugs.openjdk.java.net/browse/JDK-8223773
The proposed changeset is located at:
https://cr.openjdk.java.net/~naoto/8223773/webrev.00/
Checking the range of HourOfAmPm with the range of AmPmOfDay is
apparently incorrect. Fixing it will change the behavior of parsing
with SMART resolver style to throw a DateTimeParseException. This
is a change in which an app will start to see an exception with
incorrect data, but that is what should be in the first place.
Naoto
