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

Avoid creating Manifest when checking for Multi-Release attribute

XMLWordPrintable

    • b113
    • generic
    • generic

      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.

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

              Created:
              Updated:
              Resolved: