-
Bug
-
Resolution: Fixed
-
P2
-
9
-
b51
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8084485 | emb-9 | Roger Riggs | P2 | Resolved | Fixed | team |
| JDK-8149283 | 8u101 | Robert Mckenna | P2 | Resolved | Fixed | b01 |
| JDK-8140603 | 8u92 | Robert Mckenna | P2 | Closed | Fixed | b01 |
| JDK-8155428 | emb-8u101 | Robert Mckenna | P2 | Resolved | Fixed | b01 |
The spec says that the method isLeapYear(long prolepticYear) accepts as parameter prolepticYear which is not validated for range.
http://docs.oracle.com/javase/8/docs/api/java/time/chrono/HijrahChronology.html#isLeapYear-long-
But f.e. in the case of using one of the following values 1004, 1008, 1012, 2000, 400, 4, 400000000, 0, 96, -4, -400000000 as parameter the unexpected DateTimeException is thrown:
java.time.DateTimeException: Hijrah date out of range
Tests belonging to the JCK9 suite (not yet integrated) will fail due to this issue: api/java_time/chrono/HijrahChronology/index.html#IsLeapYear
(not integrated yet)
http://docs.oracle.com/javase/8/docs/api/java/time/chrono/HijrahChronology.html#isLeapYear-long-
But f.e. in the case of using one of the following values 1004, 1008, 1012, 2000, 400, 4, 400000000, 0, 96, -4, -400000000 as parameter the unexpected DateTimeException is thrown:
java.time.DateTimeException: Hijrah date out of range
Tests belonging to the JCK9 suite (not yet integrated) will fail due to this issue: api/java_time/chrono/HijrahChronology/index.html#IsLeapYear
(not integrated yet)
- backported by
-
JDK-8084485 Clarify java.time.chrono.Chronology.isLeapYear for out of range years
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Closed
-
- relates to
-
-
- Closed
-