JDK-8150976 : JarFile and MRJAR tests should use the JDK specific Version API
- Type: Bug
- Component: core-libs
- Sub-Component: java.util.jar
- Affected Version: 9
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2016-03-01
- Updated: 2016-05-27
- Resolved: 2016-03-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.
| JDK 9 |
|---|
9 b109Fixed  |
Related Reports
|
Blocks :
|
Description
Currently JarFile and MRJAR tests use sun.misc.Version to retrieve the major runtime version. They should be updated to use the new JDK specific Version API. Note: There is an issue, JDK-8144062, to revisit the JDK specific Version API to determine if it should be moved, or even standardized. The changes being proposed here may need to be updated, in a trivial way, in the future, but this issue is intending to break the dependency on sun.misc.Version so that JDK-8150162 can make progress. Additionally, the future refactoring will most likely be trivial.