Issue 87470 - Bundle new JRE with OOo
Summary: Bundle new JRE with OOo
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: DEV300m4
Hardware: All All
: P3 Trivial with 1 vote (vote)
Target Milestone: OOo 3.0
Assignee: Olaf Felka
QA Contact: issues@installation
: 87600 (view as issue list)
Depends on:
Reported: 2008-03-26 15:07 UTC by joachim.lingner
Modified: 2008-08-04 16:58 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-03-26 15:07:43 UTC
Replace the currently bundled JRE with the new 6u5.
Comment 1 2008-03-31 13:50:19 UTC
Included new java 6 update 5 in cws jl95
Comment 2 Olaf Felka 2008-03-31 15:03:18 UTC
*** Issue 87600 has been marked as a duplicate of this issue. ***
Comment 3 joachim.lingner 2008-04-01 13:49:31 UTC
jl->of: Please verify.
Comment 4 joachim.lingner 2008-04-01 13:50:10 UTC
Comment 5 Olaf Felka 2008-04-04 13:44:39 UTC
OF: Reverified the bundling of jre6u5.
Comment 6 Olaf Felka 2008-04-18 13:16:48 UTC
OF: OK in dev300_m9
Comment 7 kebera 2008-08-04 16:58:35 UTC
(This appears to be the root of the Duplicate chain, so please re-open it as the
fundamental problem is not fixed.)

Bundling JRE 1.6r5 clearly does not fix the problem, nor does bundling JRE
1.6r7, because by the time a given OOo is released there is a newer
security-fixed JRE. 

The installation script should fetch the latest compatible JRE.  Maybe some kind
of dynamic redirect could be put onto the OOo website to point to the right
place.  Alternatively, while installing OOo, at least ask the user if they want
to install the bundled JRE or go get the latest one or neither.

Then it is Sun's job to fix their installers to remove old versions.