This should allow us to use "proper" Mac OS JRE bundles.Īt time of writing this compiles okay, but is untested. tgz then getdown uses the Apache Commons Compress library to gunzip|untar the file (in fact this will now work for any resource in getdown.txt). tgz file extensions in the java_location URL. So, I've made some reasonable additions to getdown so that it's Application.getJavaVMResource() method will allow both. I have noticed that in java12, the file the link points at MOVES from Home/lib/jli/libjli.dylib to Home/lib/libjli.dylib.ġ) Since we cannot change install4j, we're going to have to use a JRE with the MacOS Contents/Home and the Contents/MacOS/libjli.dylib symbolic link.Ģ) Since this symbolic link might change (indications from java 12 suggest will change), the JRE unbundling should be able to replace a symbolic link. Q: Can we just put the symbolic link in once before installation and not change it in JRE updates?Ī: No. Source Code Management: This document lists ways to access the online source repository. To review, open the file in an editor that reveals hidden Unicode characters. These are the individuals who have contributed to the project in one form or another. ist This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. jar file, which cannot deal with symbolic links. This document provides information on the members of this project. I have modified getdown source to also look for a JRE bundled in java_vm/Contents/Home. Annoyingly this has to be a symbolic link, a copy of the libjli.dylib file it is pointing at doesn't work. However it still insists on wanting a Mac OS style JVM bundle with Contents/Home and importantly the symbolic link Contents/MacOS/libjli.dylib. * install4j can be configured to look for the JRE elsewhere in the Jalview.app bundle, e.g. Which doesn't use the Contents/Home dirs. It's a broad topic, you can find a lot information about it. java packager tool or launch4j), some are not (install4j). Jalview.app/Contents/Resources/app/java_vm/. it's a common problem for any platform, and solution to this are wrappers, some are free (i.e. However, this change may have consequences for your install4j projects: The application bundle that is installed by a 'Mac OS X single bundle' installer cannot be signed anymore. * getdown (sitting within the install4j app-bundle) by default installs a bundled JRE in We have implemented v2 signatures in install4j 5.1.13, so you can already create application bundles that will work with the upcoming disruptive releases of Mac OS X. Jalview.app/Contents/Resources/jre.bundleĪnd uses the Mac style JRE install that looks like: * In the default install4j Jalview.app bundle if install4j bundles a JRE it puts it in This issue discusses the conflict found between getdown's bundled JRE and install4j's bundled JRE on macOS using the DMG Jalview.app bundle method in install4j.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |