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

Avoid creating Manifest when checking for Multi-Release attribute

    XMLWordPrintable

Details

    • b113
    • generic
    • generic

    Description

      The Multi-Release feature cause a startup regression in various applications due to creating and parsing the manifest entry into a java.util.jar.Manifest - by reusing the logic the hasClassPath goes through to scan the raw manifest data for the Multi-Release: attribute we can avoid this.

      Attachments

        Issue Links

          relates to

          Sub-task - The sub-task of the issue JDK-8132734 JDK 9 runtime changes to java.util.jar to support multi-release jar files

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

          Bug - A problem which impairs or prevents the functions of the product. JDK-8165723 JarFile::isMultiRelease() method returns false when it should return true

          • P3 - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JDK-8186334 JarFile throws ArrayIndexOutOfBoundsException when the manifest contains certain characters

          • P3 - Major loss of function.
          • Closed

          Activity

            People

              redestad Claes Redestad
              redestad Claes Redestad
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: