JDK-6967423 : Hotspot support for modules image
- Type: Bug
- Component: hotspot
- Sub-Component: runtime
- Affected Version: 7
- Priority: P4
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2010-07-07
- Updated: 2011-04-23
- Resolved: 2011-04-23
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 6 | JDK 7 | Other |
|---|---|---|
| 6u21pFixed | 7Fixed  |
hs19Fixed |
Related Reports
|
Relates :
|
Description
To support JDK modularity, jdk will build new module images that will have some changes in the jdk layout. For example, the "jre" subdirectory in the JDK is removed. JDK will no longer have jar files that will be replaced with modules. Hotspot has some dependency on the layout of the legacy image that needs to be revised for module image. It includes: o Hotspot SA build has a dependency on tools.jar o the gamma launcher has hardcoded path of the JRE path o the default bootclasspath assumes the presence of rt.jar. A temporary fix to include jdk.boot module in the bootclasspath is needed to bootstrap the VM.
Comments
|