You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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?
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.
I use macOS Big Sur 11.2.3 on Intel.
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: