Is Legacy Java Se6 Runtime Safe Code Is Compiled

It would be awesome if this could be sorted out for the new release.

But please be aware that the beast.jar used in Tracer has to be compiled in Java 8 as well.

Is Legacy Java Se6 Runtime Safe Code Is Compiled

The issue is not what the code is compiled with but the script within the Mac package that works out what JVM is installed and runs it.

It doesnt pick the JVM version based on the language version of the JAR file.

On the Mac it is not sufficient to have the JRE 1.8 installed as that just has provides a browser plug-in.

To run BEAST or Tracer or any other Java desktop program it is necessary to install the JDK.

The Apple Java 1.6 install still works fine and is easier than the JDK 1.8 install.

Probably the best solution (and one I will look into for FigTree also) is including a JVM within the Mac application package.

So - I would absolutely be against compiling the code to Java 8 language unless there was an absolutely compelling case that the language features it brings are worth it (possibly for a newly written package but not for old code, I suspect).

I see no point in making the JAR incompatible with older JVMs just for the sake of it.

Today I downloaded the Tracer dmg and tried opening the app on osx 10.12.6 with java 8 as the default.

I also got the error telling me to downgrade, so the app bundler still runs the script tailored for java 6.

So your better option is to just run that, I assume an updated launcher script is in the works.

Is Legacy Java Se6 Runtime Safe For Mac