JDK-2165554 : Need manifest for every exe file in jre/bin directory
  • Type: Backport
  • Backport of: JDK-6722527
  • Component: install
  • Sub-Component: install
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2008-07-31
  • Updated: 2010-04-04
  • Resolved: 2008-10-01
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.
6u10 b31Fixed
SUGGESTED FIX http://sa.sfbay.sun.com/projects/deployment_data/6u11/2165554.1

EVALUATION This is the forward port of the 6u7 work. Additional work included removing the way java.exe and unpack200 was using manifests. They should use the template now, instead of their own private copy. jqsnotify.exe is a new deploy 6u10 file that needed a manifest. jqs.exe's manifest didn't have the #define MANIFEST_RESOURCE_ID 1, so sigcheck.exe wasn't detecting it. testcase: http://j2se.east/deployment/www/tests/1.6.0/2165554

EVALUATION The following must be done: http://sa.sfbay.sun.com/projects/deployment_data/6u7/6722527.1 plus the additional work for these files: jbroker.exe jp2launcher.exe jqs.exe jqsnotify.exe There were also some additional webrev comments that I didn't get to in 6u7.