On 05/15/2012 03:09 PM, steelej wrote:
I have been a happy user of LO for a long time but have just started to
explore Base.
I have been unable to get Base to work with the latest JRE on Windows Vista
or on W7. When I select this version in the Java options it fails to
recognise that it is a valid JRE.
Environments used for testing
Base appears to run with Java 1.6.0_32 on 32 bit W7 using LO 5.3.3 but not
with 1.7.0_04. This version is a Virtual Machine
Base also runs (more extensive testing) with LO 3.5.2.2 using Java 1.6.0_31
on a 32 bit Vista but fails to run if I select 1.7.0_04. On the first
occasion I tried on this environment LO crashed completely and would not
start - I had to go into the xml configuration file and remove the reference
to Java there.
Is there a known bug associated with the latest version of Java?
1.7.0_04 works for me w/WinXP,W7, and linux. The WinXP is running in
VMWare, the W7 is running from a partition. Can you be a little more
specific as to what is not working?
--
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
- [libreoffice-users] Re: Base and Java 1.7 - does not work (continued)
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.