JDK-8010166 : TEST_BUG: fix for 8009634 overlooks possible version strings (sun/misc/Version/Version.java)
- Type: Bug
- Component: core-libs
- Sub-Component: java.lang
- Affected Version: 7u25
- Priority: P2
- Status: Closed
- Resolution: Fixed
- Submitted: 2013-03-15
- Updated: 2013-12-17
- Resolved: 2013-03-19
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 |
|---|
7u21Fixed  |
Related Reports
|
Relates :
|
Description
It would appear that the JDK & JVM versions are actually irreconcilable (at least in any readable manner) and the previous fix neglects to take the following types of version strings into account: 24.0-b37-internal-201303141810.amurillo.hs24-b37-set-ver-fastdebug 1.7.0-internal-201303141817.amurillo.hs24-b36-jdk7u14-b-b00 I had incorrectly interpreted possible values for "identifier". In addition to that, the original code would actually interpret the HS string above incorrectly, using the 2nd occurance of b37 instead of the first. The best thing to do at this point would be to separate the version parsing code for HS & the JDK.