Yet if JRE 1.6uXX is present, when Java Options GUI is open and the a fully populated javaSettings_Windows_x86.xml is created as soon as the check box to use a Java JRE is made. LibreOffice 3.4-The folder you selected does not contain a Java runtime environment. button of the Java Options GUI and manually selecting the java\jre7\bin installation directory returns error:
In Windows, the %APPDATA%\Roaming\LibreOffice\3\user\config\javaSettings_Windows_x86.xml is created when a Tools > LibreOffice > Java check box is made to "Use a Java Runtime Environment".
On a working installation of LibreOffce 3.4.4, removal of JRE 1.6uXX, deletion of javaSettings_Windows_x86.xml configuration, and installation of JRE 1.7u01Ĭreation of javaSettings_Windows_x86.xml (and presumably javaSettings_Linux_x86.xml) is NOT being populated with Java instance details for JRE 1.7u01
Jedit mac osx jre load error windows 7#
Continuing inability of LibreOffice 3.4.4 (build 402) to detect presence of JRE when only Java 1.7u01 32-bit is present on Windows 7 sp1 64-bit. Since this bug isn't a real incompatibility but just an inability to recognize java 7 properly, I think it's pretty unfortunate that it doesn't look like it'll be fixed before you start getting tons of users running into the bug rather than just a few early adopters.Ĭan confirm. Oracle may even start offering 7u2 as the default java download. When 7u2 goes final (within a couple weeks) you'll start to see a lot of people switching away from Java 6. The only other fixes in 7u1 were security fixes 7u2 has a lot more fixes and improvements, and I've been using the 7u2 prereleases for two months now without any issues. The much-hyped bugs in the original Java 7 release (which mattered a lot to Lucene and Solr but don't affect most people and were avoidable via a command-line switch) were already fixed in 7u1 on Oct 19. No such luck it still wouldn't use the jre. Considering that was able to get LO working with Java 7 by copying the jre7 into the usual jre6 location, I thought I might be able to get LO to use jre7 by putzing around with the javasettings_$PLATFORM.xml file in the profile config directory. Same problem here LO 3.4.4 won't recognize the 7u2b11 jre. Nevertheless, in some config-file the path is still stored, and its still working. So, in my opinion, this test demonstrates, that LibO really uses the Java 7 in the former Java 6 Directory.Īs for the Options Dialog: NO, there is no Java Installation displayed. To be sure it really uses THIS version of Java, I changed the foldername of the previous v6 (now v7) installation, and then LanguageTool crashes LibO (as it cant use Java anymore). I was able to use Base, Duden Korrektor and Languagtool. Then I copied the v7 version to the path that v6 used before. I then closed LibO and uninstalled the v6 version. I had 6.0.26 installed, so that LibO 3.4.3 was able to detect the path Java 32Bit is installed to. I didn't had any v6 Versions installed with 3.4.2. > probably one of those that is being used. Are you sure? Unless you have uninstalled all previous Java versions, it's
0 kommentar(er)
