Hi :)
Oracle seem to have been treating this community as a competitor since before the split away from
OpenOffice. Apparently there have been a lot of attempts at co-operating with them but Oracle tend
to refuse to respond. Both normal Java and openJDK are run by Oracle. The LO devs have been
writing out Java dependence but that is trickier in Base.
It's possible to install Java version _21 alongside other versions and then get only LO to use the
_21. The web-browsers and other stuff will pick-up on the newer version automatically but you can
force LO to use the _21 by clicking on
Tools - Options - LibreOffice/General - Java
and then all versions of java that are installed should appear so just select the _21.
Note that some people say it's the older version and therefore unsafe but it's more recent than
ones that appear on many systems, for example Ubuntu 10.04 LTS uses version _20.
Also, the newer ones that are supposedly safer will doubtless be found to be deeply flawed and are
probably suffering security exploits right now that we will only hear about later. It seems that
the only java that is really safe is one that is not installed anywhere.
Just my 2cents!
Regards from
Tom :)
--- On Thu, 13/10/11, Alexander Thurgood <alex.thurgood@gmail.com> wrote:
From: Alexander Thurgood <alex.thurgood@gmail.com>
Subject: [libreoffice-users] Re: Base - using external database tables
To: users@global.libreoffice.org
Date: Thursday, 13 October, 2011, 10:09
Le 13/10/11 10:54, John Talbut a écrit :
Hi John,
I am aware of this. I am not really interested in who is to blame, it
needs sorting for current versions of JDK. If you or anyone has any
idea what the change is in JDK that has led to this problem please
answer at http://lists.freedesktop.org/mailman/listinfo/libreoffice
where I have asked this specific question.
Well, that will probably be rather hard to answer since the LibreOffice
project doesn't develop the Java runtime engine or development kit. Only
those who work on the JDK/JRE are likely to know why things suddenly
went pear-shaped, and as far as I know no-one amongst the LibreOffice
development is involved in Oracle's Java development. I imagine that the
same could be said for those former OpenOffice.org developers who worked
for Oracle and are now working at IBM, Redhat or wherever, as they were
after all, separate projects.
In the past, when similar events happened with OpenOffice.org, AFAIK it
was the JDK that Sun/Oracle had to fix, and not the other way around.
From what I remember, it was often some accessibility code change within
the JDK that caused the problems. Perhaps, and I say just perhaps, you
could check to see whether you have any accessibility options activated
(system-wide), and then turn them off to see if that brings a mild
improvement ? If not, then I know no other solution other than a
downgrade (or dual installation with an earlier version) of the JDK.
Alex
--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Context
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.