Mac OSX 10.8 + LO v4.0.1 and Java 7 support?

LibreOffice currently supports only apple java 1.6 on Mac OS 10.8. With java 7 installed (jre and jdk) it asks for Apple Java SE 1.6, same with compiling a plugin I’m developing. I can compile the plugin with my custom scripts using 7 but LO explodes when attempting to use the plugin.

I have replicated this on 4-5 different Macs of different model, same java 7 subvariant. With and without java 6 SE installed, 10.8.2 and 10.8.3, using LO 4.0.1.

Is there a bug ticket already tracking java 7 compatability on Mac 10.8 ?

I don’t think @rl is giving us full details.

Java 6 SE was automatically included up to 10.8. So if an upgrade was done from 10.7 to 10.8, then the machine would automatically have java from the previous version.

Starting with 10.8, the java 6 SE and stubs are the only things included (assuming a fresh installation, not upgrade). The stubs actually link to the apple java installer, so, by running javac the first time, you get a GUI popup prompting you to install.

Apple adds special sauce to their java, breaking write-once run everywhere.

Also, apple’s java is in a different directory tree:
versus oracle’s

Structure of the home directory is different also, oracle uses the unix bin directory and apple uses Commands directory.

I have java_home and $JAVA_HOME set to java 7, as well as all soft links relating to java pointing to 7, and yet, when running LO, it still manages to find java 6 since the installer pops up, meaning this path is hardcoded somewhere. This only happens when using Calc and attempting to run a custom function, so may be related to the UNO bridge.

The LO SDK also finds the apple home directory, as if hardcoded. When running setsdkenv_unix, if you manually specify JDK 7 home, it will not accept it.

Hi @tjones248,

Per this question, @rl says:

I use LibreOffice with the latest Java 7 on Mac OS X 10.8.1 on hardware from 2008 and 2010.

So it looks like an older build of LO 3.6 worked on 10.8 + Java 7, however this could still be an issue with LO 4.0.1, OSX 10.8.2/3, or even a Java update…

@rl – Have you upgraded to 10.8.2 or 10.8.3? Could you update to LO 4.0.1 and let us know if you experience the same problem as described here?