JDK-8152733 : Avoid creating Manifest when checking for Multi-Release attribute
- Type: Bug
- Component: core-libs
- Sub-Component: java.util.jar
- Affected Version: 9
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2016-03-25
- Updated: 2017-08-17
- Resolved: 2016-03-28
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 b113Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
The Multi-Release feature cause a startup regression in various applications due to creating and parsing the manifest entry into a java.util.jar.Manifest - by reusing the logic the hasClassPath goes through to scan the raw manifest data for the Multi-Release: attribute we can avoid this.