-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MacOs ready to run 4.0.1 - RC3 release - contains Windows JRE #7
Comments
Hi, there was an error in my "cross platform jlink executable " script that generated the wrong Java JDK for macOS. I uploaded a new version of https://armatiek.nl/downloads/xslweb/xslweb-ready-to-run-v4.0.1-RC3-osx-x64.tar.gz containing the correct JDK. I can't test this new upload right now (don't own a Mac and my VirtualBox image is out of order :-(), Will you let me know if this new upload solved your problem? Regards, |
Hi Maarten, The new version of https://armatiek.nl/downloads/xslweb/xslweb-ready-to-run-v4.0.1-RC3-osx-x64.tar.gz works. On my machine it generates another issue though. The default security manager (Gatekeerp) for MacOS doesn't know the developer for Java and all of its libraries. Probably a certificaiton issue. Java and each of the libraries need to be accepted manually for the java environment to work and xslweb to start. further information: Keep up the good work. 👍🏻 Richard |
Hi Richard, Thanks, I will! It's time to get my VirtualBox macOS image working again ;-) Maarten |
When starting XSLWeb with bin/run-service.sh, an error is shown:
run-service.sh: line 10: ......./jre/bin/java: No such file or directory.
When I looked into the specified directory I found java.exe (but not java). The same directory also contained some dll files. I asume the Windows JRE is supplied instead of the Osx (*nix?) jre.
Work around:
On my Mac I use Jenv as a command-line tool to manage java versions for all applications. I was able to work around this issue by changing JAVA_PATH to java and comment out the JAVA_HOME line.
This allowed me to use the global jenv settings, in this case for java 15.
The text was updated successfully, but these errors were encountered: