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

Avoid reading security properties eagerly on Manifest class initialization

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: P3
    • Resolution: Fixed
    • Affects Version/s: 12
    • Fix Version/s: 12
    • Component/s: core-libs
    • Subcomponent:
    • Introduced In Build:
      b14
    • Resolved In Build:
      b15

      Description

      JDK-8207768 moved some property initialization that depends on the security properties file into Manifest.<clinit>, meaning that any jar file with a manifest will load the security properties eagerly. However, this property is only read if/when an exception occurs, so it can profitably be initialized lazily.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                redestad Claes Redestad
                Reporter:
                redestad Claes Redestad
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: