JDK-6257124 : Update JAVAUPDATE command line option in JRE installer for PC-OEMs
- Type: Bug
- Component: install
- Sub-Component: install
- Affected Version: 5.0u4,5.0u6
- Priority: P3
- Status: Closed
- Resolution: Fixed
- OS: windows_xp
- CPU: x86
- Submitted: 2005-04-19
- Updated: 2010-04-04
- Resolved: 2006-11-02
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| Other | JDK 6 |
|---|---|
| 5.0u5Fixed | 6 b36Fixed  |
Related Reports
|
Duplicate :
|
Description
Currently, many PC-OEMs use the JAVAUPDATE=0 option to turn off Java Update for bundling. However, what we really want is for PC-OEMs to turn off Java Update but enable Java Plug-in to prompt users to turn on Java Update again on first run. We should change the JRE installer to turn off Java Update but enable first-run prompt in Java Plug-in if JAVAUPDATE=0 is passed. ###@###.### 2005-04-19 00:31:41 GMT
Comments
|