JDK-7184019 : drop installer.dll in the jre bin dir, so it's up-to-date during uninstall after PnP
- Type: Bug
- Component: install
- Sub-Component: install
- Affected Version: 8
- Priority: P2
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2012-07-13
- Updated: 2013-06-26
- Resolved: 2012-09-17
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.
| JDK 7 | JDK 8 |
|---|---|
7u40Fixed  |
8 b57Fixed |
Related Reports
|
Relates :
|
Description
Consider the following: 1. Install Java 8 2. Patch-In-Place to 8u5 3. Uninstall 8u5 The 8u5 uninstaller will be running the installer.dll that was built with 1.8.0. This is a design flaw with the current Patch-in-place model. The installer.dll is part of the MSI binary table which gets cached in a hidden Windows Installer directory after install. When we do PnP, we do not currently use a MSP to patch this cached msi/installer.dll. I think the best short term solution for this is to drop the installer.dll into the jre/bin dir (rather than in the msi binary table). Then the msi uninstall will call UninstallJava() from the jre/bin/installer.dll file.
Comments
|