Date: prev next · Thread: first prev next last
2016 Archives by date, by thread · List index

[tdf-discuss] Re: Java still broke on LibreOffice 5.1.1

Larry, *

Larry Gusaas wrote
LibreOffice 5.1.1 on Macs still doesn't recognize Java Runtime Environment
(JRE 1.8.0_73 & OS X 

You need to fix this bug. Can't use database without JRE.

As noted in the thread LibreOffice  User ML  2016-02-10 thread
, for the 5.1  release of LibreOffice the JRE installed with the JDK is now
required for use of the HSQLDB and the remaining bundled Java apps

Moving it over here to the LibreOffice Discus ML is fine.  Cordial
discussion is always welcome.

However, the reality remains that until Oracle and Apple complete work on
removing the Java Runtime Support framework unique to OS X (now Oracle's
responsibility and marked for implementation for Java 9) use of the JDK
deployed JRE (the NeoOffice provided patches) as now implemented in
LibreOffice is where things are.  Not ideal, but a WORKSFORME workaround.

We can't fix what Oracle and Apple broke (rather omitted), and we probably
won't revert to the status quo of 5.0 and the 4.x release  as that required
its own set of work arounds--i.e.  requiring install of Apples unsupported
JRE in addition to a Java 8 JRE.

That is the reality.



View this message in context:
Sent from the Discuss mailing list archive at

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.