-
Bug
-
Resolution: Fixed
-
P3
-
6u5
-
b07
-
generic
-
windows
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2199107 | 7 | Jennifer Zuo | P3 | Closed | Fixed | b64 |
In deploy/src/plugin/win32/regutils/RegInstall.cpp, RegCurrentVersionKeys:
If installType != 0, IDR_RegCurrentVersion is being used. It is clear that this should be IDR_RegSDKCurrentVersion. IDR_RegSDKCurrentVersion is unreferenced in the current code.
The expected side effect is if the JDK is installed without the associated public JRE, we will pollute the registry with a bunch of incorrect and/or corrupt keys.
Testing indicates that for an unknown reason this does not happen. It is possible that the unresolved macros cause the application of the registry script to fail. Currently it is unknown why the HKLM/SOFTWARE/JavaSoft/Java Development Kit/Current registry key is being correctly created.
If installType != 0, IDR_RegCurrentVersion is being used. It is clear that this should be IDR_RegSDKCurrentVersion. IDR_RegSDKCurrentVersion is unreferenced in the current code.
The expected side effect is if the JDK is installed without the associated public JRE, we will pollute the registry with a bunch of incorrect and/or corrupt keys.
Testing indicates that for an unknown reason this does not happen. It is possible that the unresolved macros cause the application of the registry script to fail. Currently it is unknown why the HKLM/SOFTWARE/JavaSoft/Java Development Kit/Current registry key is being correctly created.
- backported by
-
JDK-2199107 Wrong registry script referenced in Windows JDK installer
- Closed