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

Contents/MacOS/libjli.dylib cannot be a symlink

    XMLWordPrintable

Details

    • b27
    • os_x

    Backports

      Description

        To be able to fully sign and notarize a jdk-bundle on MacOS, the file Contents/MacOS/libjli.dylib cannot be a symlink. The easy fix is to simply make it a normal file. Longer term we will evaluate what this file is actually needed for, but for now, we just need to make the JDK compatible with the new requirements from Apple.

        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-8236009 Contents/MacOS/libjli.dylib cannot be a symlink

            • 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-8236171 Contents/MacOS/libjli.dylib cannot be a symlink

            • 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-8236253 Contents/MacOS/libjli.dylib cannot be a symlink

            • 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-8236550 Contents/MacOS/libjli.dylib cannot be a symlink

            • 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-8238977 Contents/MacOS/libjli.dylib cannot be a symlink

            • 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-8239261 Contents/MacOS/libjli.dylib cannot be a symlink

            • 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-8241341 Contents/MacOS/libjli.dylib cannot be a symlink

            • 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-8244892 Contents/MacOS/libjli.dylib cannot be a symlink

            • 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-8246920 Contents/MacOS/libjli.dylib cannot be a symlink

            • 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-8248699 Contents/MacOS/libjli.dylib cannot be a symlink

            • 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-8248961 Contents/MacOS/libjli.dylib cannot be a symlink

            • 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-8251733 Contents/MacOS/libjli.dylib cannot be a symlink

            • 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-8237972 Contents/MacOS/libjli.dylib cannot be a symlink

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

            Bug - A problem which impairs or prevents the functions of the product. JDK-8238225 Issues reported after replacing symlink at Contents/MacOS/libjli.dylib with binary

            • P3 - Major loss of function.
            • Resolved

            Activity

              People

                erikj Erik Joelsson
                erikj Erik Joelsson
                Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: