Compiling to Java 8 and running on JVM 8 are two different things. 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 doesn't 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.
![]()
There's not much of a security issue if you're not running Java applets with Java 6. That said, all of the JetBrains products will run fine on Java 7 and Java 8 (not counting JDK bugs). Edit the Info.plist file in the application package and look for this stanza: JVMVersion 1.6.
![]()
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.A.
I am SO disappointed, I was very excited to get my new laptop & have worked hours setting it up. Only problem I had was CS5, so very strange because I have the same operating system on my other computers and they work just fine. I can't spend any more time on it so I finally bit the bullet & got Adobe Cloud, don't like the idea of a subscription. But with my new MacBook Pro, old CS5 didn't work on macOS Sierra and I think all software is going to go that route eventually.
Thank you for all the links and help!
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |