| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8084638 | emb-9 | Roger Riggs | P4 | Resolved | Fixed | team |
The assignment to epochMonth in java/time/chrono/HijrahChronology.java is a dead code. It happened after following fix https://bugs.openjdk.java.net/browse/JDK-8067800
public boolean isLeapYear(long prolepticYear) {
checkCalendarInit();
if (prolepticYear < getMinimumYear() || prolepticYear > getMaximumYear()) {
return false;
}
int epochMonth = yearToEpochMonth((int) prolepticYear);
int len = getYearLength((int) prolepticYear);
return (len > 354);
}
public boolean isLeapYear(long prolepticYear) {
checkCalendarInit();
if (prolepticYear < getMinimumYear() || prolepticYear > getMaximumYear()) {
return false;
}
int epochMonth = yearToEpochMonth((int) prolepticYear);
int len = getYearLength((int) prolepticYear);
return (len > 354);
}
- backported by
-
JDK-8084638 Dead code in java.time.chrono.Chronology.isLeapYear after fixing JDK-8067800
-
- Resolved
-
- relates to
-
JDK-8067800 Clarify java.time.chrono.Chronology.isLeapYear for out of range years
-
- Closed
-