Recommended version of Java?

The fact is, Libreoffice, for a long time, simply did not work at al

with Java7.

Huh? Really? Which issue number was that? I can't believe that any LO version had been released with such a show stopper issue.

The problem is/was much more subtle than the OP implied.

Java functioned correctly for some things, but not others. Change the
build, and it worked correctly for a different set of things, but failed
for the original set. Switch to a third build, and there was a different
set of failures and successes.

The only viable fix, is to completely rip Java out, and prohibit both
extensions, and future code submissions that require Java.

jonathon

  * English - detected
  * English

  * English

<javascript:void(0);>
and politly, but firmly prohibit any extenion that requires Java, and
all coide that calls Java. IOW, make Java a prohibited language.

Well, please reconsider your statement in light of the requirement for
LibreOffice 4.3.3 on OSX Yosemite and current master 440 alpha to use an
end of life Apple Java 6, in addition to Java 1.8, to remain even
remotely stable with the default bundled extensions that require Java.

The Java 1.8 invocation problem is Oracle's bug (known, slated for fix
in Java 9), and the fact that on OSX LibreOffice bundles extensions
requiring Java is the LibreOffice projects responsibility.

FWIW :

https://bugs.freedesktop.org/show_bug.cgi?id=74877

Alex

Hi :slight_smile:
Back in 2011, the first several versions of Java 1.7xxxx had compatibility
issues with lots of software including LibreOffice. So that was around LO
3.4.3 and earlier.

Java 1.7.0_0, Java 1.7.0_1, Java 1.7.0_2, Java 1.7.0_3 and i think Java
1.7.0_4 (maybe even 5 too) were all compromised before release date which
was particularly bad because 1.6.xx created serious problems on some
platforms. Through intense testing and discussions on this list we found
that around 1.6.xx24 and onwards there were hefty slow-downs whereas
1.6xx21 let LO run quite quickly. I can't remember exactly which version
was found to be optimal.

While we were waiting for 1.7.xx to become safe enough to use one in their
earlier branch, a 1.6xx29(?) was suddenly fast again on Windows (and i
think Linux too) but had horrendous malware issues on Macs. Macs were
vulnerable to only 2 malware threats that entire year and at least 1 of
those was due to Java 1.6xx. It was serious enough that press articles
reported that many people were starting to have to run 'anti-virus' on Macs
and many articles promised it was the end of Macs security (purportedly
'security through obscurity') and suggested that Macs would henceforth have
the same problem Windows has. It was then at least 1-2 years before Macs
had any other malware issues despite continuing rapid growth of
market-share.

It doesn't seem to have been such a serious issue since then but most times
when people have had problems with Java, or problems with LO crashing, it
has been solved by people on this mailing list suggesting to switch off
Java and consider removing it.

We don't seem to need to track specific versions of Java quite as closely
as we once did. When we did track it the information outside of this
mailing list was abysmal.
Regards from
Tom :slight_smile:

Thank you. Just like Florian Reisinger I was unaware of this issue with
OSX.

Let me rewrite the 3 answers since I still don't know Tanstaafl's
operating system.

1. Always use a 32 bit JRE with LO on Windows. It may be your second or
third JRE which is perfectly OK. Nothing wrong with many JREs for
different purposes.
2. Mac users need an outdated Java 6 in addition to their default JRE
until Oracle fixed a bug.
3. Use whatever JRE comes from the distributor of your Linux platform.

Nope. There was a considerable time period when the current version of
Libreoffice didn't even *see* a Java7 installation.

Nope.. no clue what your point was, since you snipped necessary context.

The first (and only) valid answer I got was from V Stuart Foote...

And thanks Stuart - you totally answered my question, but I neglected to
thank you.

The reply from Florian was not unhelpful, but certainly didn't fully
answer my question.

I never got a valid answer from you, Andreas, just a snarky reply.

documentation@global.libreoffice.org