JDK-6184715 : JDK product .exe and .dll file version must include the build number
- Type: Bug
- Component: deploy
- Sub-Component: deployment_toolkit
- Affected Version: 5.0u2,5.0u3,6
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- OS: generic,windows
- CPU: generic
- Submitted: 2004-10-26
- Updated: 2010-04-05
- Resolved: 2004-12-15
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.
| Other | JDK 6 |
|---|---|
| 5.0u2Fixed | 6 b16Fixed  |
Related Reports
|
Duplicate :
|
|
|
Duplicate :
|
Description
Name :- vj102386 Date :- 2004-10-26 ----------------------------------------------------------------------- Currently all the .dll and .exe files that we ship as part of our jdk product contains the following file version. For Eg :- 6.0 release ----------- 1.6.0.0 1.5.0_01 release ---------------- 1.5.0.10 Since all the 6.0 release binary would contain 1.6.0.0, we cannot identify the build number by looking into the file version. From MS crash collection database we only have access to file version and the product. ###@###.### 10/26/04 19:23 GMT javaws.exe also doesn't have any version information. ###@###.### 11/3/04 23:58 GMT
Comments
|