Issue 99618 - prevent invalidating the java settings when updating to 3.1
Summary: prevent invalidating the java settings when updating to 3.1
Status: CLOSED FIXED
Alias: None
Product: udk
Classification: Code
Component: code (show other issues)
Version: OOo 1.0.0
Hardware: All All
: P3 Trivial (vote)
Target Milestone: OOo 3.1
Assignee: Olaf Felka
QA Contact: issues@udk
URL:
Keywords:
Depends on:
Blocks: 95768
  Show dependency tree
 
Reported: 2009-02-25 12:52 UTC by joachim.lingner
Modified: 2009-04-23 12:35 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description joachim.lingner 2009-02-25 12:52:14 UTC 
See the mail thread at 
http://www.openoffice.org/servlets/ReadMsg?list=releases&msgNo=13345
and particularly 
http://www.openoffice.org/servlets/ReadMsg?list=releases&msgNo=13367


This issue is about setting the <updated> element in the javavendors.xml back to
its previous value.
Comment 1 joachim.lingner 2009-02-25 12:52:59 UTC 
.
Comment 2 joachim.lingner 2009-02-25 13:06:16 UTC 
see also issue 99619
Comment 3 Olaf Felka 2009-02-26 15:53:31 UTC 
@ jl: What' about this issue? Is it fixed already or just started?
Comment 4 joachim.lingner 2009-02-26 16:02:00 UTC 
.
Comment 5 Olaf Felka 2009-03-04 10:16:26 UTC 
of: OOo 3.0 doesn't work with JRE 1.4.x. So we don't have a problem when
updating from 3.0 to 3.1. What might be a problem is, that we migrate the Java
settings of OOo 2.x with an selected JRE 1.4.x. We  should turn of this
migration. I'm not sure whether this still a 3.1 stopper.
Comment 6 Olaf Felka 2009-03-04 10:17:40 UTC 
reopening
Comment 7 joachim.lingner 2009-03-05 15:28:19 UTC 
Yes. Migration of the OOo settings must not happen - or completely different
mechanism is needed.
The migration may now causes now an error message at the end of the first start
wizard, saying that one needs to select a JRE in the options dialog and the
current is defective. On unix the soffice scripts sets the LD_LIBRARY_PATH to
contain several path to the JRE installation. Only this JRE must be used by OOo.
Setting the path must be done before OOo is started. When the user data are
migrated, then the JRE from those settings are used which may be different then
the one for which the LD_LIBRARY_PATH was set. The initialization of Java in OOo
will fail and it appears that it is defect.
The fix is to prevent this migration.
Comment 8 joachim.lingner 2009-03-06 11:26:59 UTC 
@of: please verify.
Comment 9 joachim.lingner 2009-03-06 11:34:09 UTC 
.
Comment 10 Olaf Felka 2009-03-06 14:17:51 UTC 
of: Without migrating the java settings of OOo 2.x no problem on OOo 3.1 start
in cws jl119.
Comment 11 joachim.lingner 2009-03-19 13:20:55 UTC 
adding to blocker issue
Comment 12 Olaf Felka 2009-04-23 12:35:20 UTC 
Looks good in OOO310_10.