Results 110 comments of Yevgeny Kazakov

@HowardLander to get a little bit more info, could you try to launch the Protege app from the terminal. For this, just open the terminal, navigate to the Protege app...

@HowardLander > java -version java version "11.0.11" 2021-04-20 LTS > […](#) Looks like you run the java installed on the system, not the one from the JRE folder. You need...

OK, looks good! Now from the `/Contents/Java` subfolder try to run the following command (just copy & paste in the terminal): ``` ../Plugins/JRE/Contents/Home/jre/bin/java \ -classpath bundles/guava.jar:bundles/logback-classic.jar:bundles/logback-core.jar:bundles/slf4j-api.jar:bin/org.apache.felix.main.jar:bin/maven-artifact.jar:bin/protege-launcher.jar \ org.protege.osgi.framework.Launcher ```

Great! So it looks like the app somehow does not find the JRE within the subfolder. Just to double check, can you paste the content of the file `./Contents/Info.plist`. Oh,...

The file seems right. Try installing [Oracle JRE 1.8](https://www.java.com/en/download/manual.jsp) and removing these two lines from `./Contents/Info.plist`: ``` JVMRuntime JRE ``` Then Protege should pick up the system java instead of...

@HowardLander You can install several versions of java on your mac and easily switch between them by setting `JAVA_HOME` to whatever you need. See for example [here](https://stackoverflow.com/a/24657630). I cannot reproduce...

> I had to change the PATH variable as well as change JAVA_HOME Hmm.. normally you do not need to change the path. The java executable in `/usr/bin/java` executes the...

Well, looks like JavaAppLauncher (or whatever it is using) is broken after all. B.t.w., in your last command, you did not use the new JRE. With the new JRE it...

> Copying Java from MacOS into the Protété.app didn't fix the Problem. I'm still getting the same Error. Just to confirm: you also changed the lines in `Info.plist` right?

@AneesHl @HowardLander are you talking about the same machine? ;-) It is strange that `/usr/libexec/java_home -V` does not find the installed JDKs, in particular those in `/Library/Java/JavaVirtualMachine/`. This is what...