Apache OpenOffice (AOO) Bugzilla – Issue 14282
jvmsetup: Java could not be found in 1.1 Beta 2
Last modified: 2003-06-25 15:39:31 UTC
Hi, on SuSE Linux 8.2 with pavel@pavel:/data/pavel/OpenOffice.org1.1Beta2/program> rpm -qa|grep -i java BlackdownJava2-JRE-1.4.1-3 java2-jre-1.4.1-23 java2-1.4.1-23 JRE could not be found in jvmsetup. Both 1.0.3 and 1.1 Beta 1 can find it in /usr/lib/java/jre/. Do you see the same? The same behavior was observed also on SuSE Linux 8.0 with 1.3.1 (old versions work, Beta 2 doesn't). Even if I browse to /usr/lib/java/jre/ JRE is not found there. Kevin told me that there is a bug in scp/source/office/files.scp. Why do we exclude 1.4.1 for OOo specifically on Linux/INTEL? ExcludeVersion=1.4.1
reassigned.
The content of the listbox of the java setup should initially contain supported versions only, which currently are Sun Javas and compatible Javas (including same versioning scheme) which meet our version requirement. By using the "Browse" button one can choose a Java installation "by hand". Then we have these scenarios: 1.A SUN Java or compatible Java which meets the version requirement was selected. It will be represented as the other Java installations in the list box. If the selected Java is already present, then nothing happens. 2.A SUN Java or compatible Java which does not meet the version requirement was seleected. It will be represented as the other Java installations in the list box. If the selected Java is already present, because it was already added to the list by means of the "browse" functionality, then nothing happens. 3. A none compatible Java was selected. The representation depends on the information which can be gained from that Java, such as JRE or SDK, version, and accessibility support. If that information is available than it is displayed. The version string will be available if the java supports the version option (java -version) and the output contains the version in the first line of its output and is enclosed in quotes. For example java version "1.4.1" This may lead to the display of useless content. JL->CJ: Can you confirm this?
Fix will make it into RC.
Kai, could you please tell how did you fixed it so we can provide it for our users in Beta2 so they can actually use it? I can in turn tell you if it is OK or not. Thanks.
Pavel, The internal API which we use to find Java installations will be relaxed in a sense that Javas are recognized which are not 100% SUN compatible. In case of Blackdown, the version string does not correspond to a SUN specification. A workaround for now is to edit the <office-dir>/user/config/javarc. There you need to adapt the entries Home RuntimeLib JavaLibPath
fixed in srx644 cws uno4
reopen
fixed in cws uno4
jl->of: Please verify.
Looks good for me in cws uno4. With the browse option I can point jvmsetup to blackdow java and it was detected.
Verified.
*** Issue 14823 has been marked as a duplicate of this issue. ***
*** Issue 15152 has been marked as a duplicate of this issue. ***
*** Issue 14439 has been marked as a duplicate of this issue. ***
*** Issue 15661 has been marked as a duplicate of this issue. ***
OK in RC.