-
Bug
-
Resolution: Fixed
-
P3
-
8, 11.0.6, 14, 15
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8238562 | 14.0.2 | Erik Joelsson | P3 | Resolved | Fixed | b01 |
JDK-8239269 | 14.0.1 | Erik Joelsson | P3 | Resolved | Fixed | b05 |
JDK-8241342 | 13.0.3 | Erik Joelsson | P3 | Resolved | Fixed | b01 |
JDK-8238871 | 11.0.8-oracle | Erik Joelsson | P3 | Resolved | Fixed | b01 |
JDK-8239263 | 11.0.7-oracle | Erik Joelsson | P3 | Resolved | Fixed | b05 |
JDK-8238772 | 11.0.7 | Christoph Langer | P3 | Resolved | Fixed | b03 |
JDK-8248700 | openjdk8u272 | Erik Joelsson | P3 | Resolved | Fixed | b01 |
JDK-8248962 | 8u271 | Erik Joelsson | P3 | Resolved | Fixed | b01 |
JDK-8238638 | 8u261 | Erik Joelsson | P3 | Resolved | Fixed | b01 |
JDK-8244893 | 8u251 | Erik Joelsson | P3 | Resolved | Fixed | b34 |
JDK-8251734 | emb-8u271 | Erik Joelsson | P3 | Resolved | Fixed | team |
JDK-8246947 | emb-8u261 | Erik Joelsson | P3 | Resolved | Fixed | team |
One problem reported is when trying to launch Eclipse IDE bundles. The VM cannot be created when using the new bundle structure.
There was also a case reported where the customer has a custom launcher that uses CFBundleLoadExecutableAndReturnError and CFBundleGetFunctionPointerForName for resolving and invoking "JNI_CreateJavaVM".
It is also unclear whether Apple really requires a symlink-free bundle for notarization. Up to now I got reports that people could notarize bundles with symlink, still.
If the symlink requirement will definitely be enforced, I assume libjli must be fixed to be able to handle the new MacOS bundle structure.
- backported by
-
JDK-8238562 Issues reported after replacing symlink at Contents/MacOS/libjli.dylib with binary
- Resolved
-
JDK-8238638 Issues reported after replacing symlink at Contents/MacOS/libjli.dylib with binary
- Resolved
-
JDK-8238772 Issues reported after replacing symlink at Contents/MacOS/libjli.dylib with binary
- Resolved
-
JDK-8238871 Issues reported after replacing symlink at Contents/MacOS/libjli.dylib with binary
- Resolved
-
JDK-8239263 Issues reported after replacing symlink at Contents/MacOS/libjli.dylib with binary
- Resolved
-
JDK-8239269 Issues reported after replacing symlink at Contents/MacOS/libjli.dylib with binary
- Resolved
-
JDK-8241342 Issues reported after replacing symlink at Contents/MacOS/libjli.dylib with binary
- Resolved
-
JDK-8244893 Issues reported after replacing symlink at Contents/MacOS/libjli.dylib with binary
- Resolved
-
JDK-8246947 Issues reported after replacing symlink at Contents/MacOS/libjli.dylib with binary
- Resolved
-
JDK-8248700 Issues reported after replacing symlink at Contents/MacOS/libjli.dylib with binary
- Resolved
-
JDK-8248962 Issues reported after replacing symlink at Contents/MacOS/libjli.dylib with binary
- Resolved
-
JDK-8251734 Issues reported after replacing symlink at Contents/MacOS/libjli.dylib with binary
- Resolved
- relates to
-
JDK-8235687 Contents/MacOS/libjli.dylib cannot be a symlink
- Resolved
-
JDK-8238534 Deep sign macOS bundles before bundle archive is being created
- Resolved
- links to
-
Commit openjdk/panama-foreign/f1332640