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
Im using Mojave 10.14.6 with several versions of Java on my machine.
Lately (in the meantime I've installed Java 14) I got a crash report and a Java security error.
The error was something like "Not allowed to run application without certificate..."
I think ugs should be aware of JAVA_HOME | JDK_HOME...
However - I was able to solve the problem by:
in my .bashrc:
export JAVA8_HOME=/usr/libexec/java_home -v 1.8
export JAVA_HOME=$JAVA8_HOME
export JDK_HOME=$JAVA_HOME
Thats interesting that overriding the jdkhome is part of the problem. Instead of setting jdkhome in the launcher script (which is a build artifact) would suggest setting it in ugsplatform.conf.
I tried running UGS on OS X Catalina with both Java 11 and Java 14. Both versions of Java resulted in the UGS crashing. I installed Java 8 and followed @MikeMitterer's steps and was able to successfully launch UGS without it crashing.
However, I did not want to set Java on my machine to 1.8. Following advice from @winder to configure jdkhome in ugsplatform.conf, this line does the trick for me:
jdkhome="`/usr/libexec/java_home -v 1.8`"
My machine is configured to use Java 14, but UGS is running against Java 8.
Im using Mojave 10.14.6 with several versions of Java on my machine.
Lately (in the meantime I've installed Java 14) I got a crash report and a Java security error.
The error was something like "Not allowed to run application without certificate..."
I think ugs should be aware of JAVA_HOME | JDK_HOME...
However - I was able to solve the problem by:
in my .bashrc:
export JAVA8_HOME=
/usr/libexec/java_home -v 1.8
export JAVA_HOME=$JAVA8_HOME
export JDK_HOME=$JAVA_HOME
adding the following lines to
ugsplatform
:Specifications
Version
I tried both UGS nightly (2020 04 06) and Stable 2019 08 14
Operating system
Mac Mojave 10.14.6
The text was updated successfully, but these errors were encountered: