Issue 93939 - Automatically choose a different JRE if the used one was uninstalled
Summary: Automatically choose a different JRE if the used one was uninstalled
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: DEV300m31
Hardware: All All
: P3 Trivial (vote)
Target Milestone: OOo 3.1
Assignee: Olaf Felka
QA Contact: issues@framework
: 83140 88225 (view as issue list)
Depends on:
Blocks: 95768
  Show dependency tree
Reported: 2008-09-16 08:52 UTC by joachim.lingner
Modified: 2009-10-19 10:31 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description joachim.lingner 2008-09-16 08:52:08 UTC
I know there exist an issue for this somewhere but I could not find it.


-plugin should have a function


-because of javaldx needs to call it every time this function should offer a
"quick" mode.
Comment 1 joachim.lingner 2008-09-16 09:04:56 UTC
Should we have a checkbox in the Java options reading:

"Automatically chose workin JRE"

Meaning that in case the JRE was uninstalled, VM Library could not be
loaded,etc. that a different JRE is used. This would override the user's JRE
Comment 2 joachim.lingner 2008-12-09 14:29:29 UTC
Comment 3 joachim.lingner 2009-03-06 09:28:36 UTC
For the user it looks like the javasettings have been lost everytime they
install a new JRE. Beginning with jre6u13, it will remove the previous version
(for example jre 6u12).
Comment 4 joachim.lingner 2009-03-06 11:24:41 UTC
Correction: On Windows the JRE 6u13 uninstalls 6u12 even if the user chooses a
different folder. When the JRE is installed with OOo then it is in the same
localtion as the 6u12 and Java works in OOo. Only the java options page does not
show the 6u12 anymore and the 6u13 is not selected.

The GUI installer on Linux always uses rpm -U to install the JRE. This causes
the previous version to be uninstalled. In this case the user will see the "java
defective" message after updating OOo (including JRE). But this problem is quite

Setting target to 3.2
Comment 5 joachim.lingner 2009-03-10 13:35:50 UTC
3.1 again.
Comment 6 joachim.lingner 2009-03-19 12:23:41 UTC
@of: Please verify.
Comment 7 joachim.lingner 2009-03-19 13:17:47 UTC
adding to blocker issue
Comment 8 Olaf Felka 2009-03-24 10:42:37 UTC
of: The fix looks good in cws jl119.
Comment 9 joachim.lingner 2009-03-31 12:35:33 UTC
*** Issue 83140 has been marked as a duplicate of this issue. ***
Comment 10 Olaf Felka 2009-04-23 12:35:38 UTC
ok in OOO310_m10
Comment 11 joachim.lingner 2009-10-19 10:31:48 UTC
*** Issue 88225 has been marked as a duplicate of this issue. ***