Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8067800

Clarify java.time.chrono.Chronology.isLeapYear for out of range years

    XMLWordPrintable

Details

    • b51
    • Verified

    Backports

      Description

        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)



        Attachments

          Issue Links

            backported by

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8084485 Clarify java.time.chrono.Chronology.isLeapYear for out of range years

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8149283 Clarify java.time.chrono.Chronology.isLeapYear for out of range years

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8155428 Clarify java.time.chrono.Chronology.isLeapYear for out of range years

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8140603 Clarify java.time.chrono.Chronology.isLeapYear for out of range years

            • P2 - Crashes, loss of data, severe memory leak.
            • Closed
            relates to

            Bug - A problem which impairs or prevents the functions of the product. JDK-8076441 Dead code in java.time.chrono.Chronology.isLeapYear after fixing JDK-8067800

            • P4 - Minor loss of function, or other problem where easy workaround is present.
            • Closed

            Activity

              People

                rriggs Roger Riggs
                ostrizhe Olga Strizhenko (Inactive)
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: