JDK-6722527 : Need manifest for every exe file in jre/bin directory
  • Type: Bug
  • Component: install
  • Sub-Component: install
  • Affected Version: 6u10
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: windows_vista
  • CPU: generic
  • Submitted: 2008-07-03
  • Updated: 2010-04-04
  • Resolved: 2008-09-25
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.
6u10Fixed 7Fixed
Related Reports
Relates :  
Relates :  
Relates :  
Relates :  
In order to pass OEM ready certification every executable file under jre/bin needs to have manifest file that defines the execution level (Req 1.1).

SUGGESTED FIX This is the follow up fix for 6722527. The fix is to add manifest to the three files in the install ws. They are the patchjre.exe, zipper.exe and launcher.exe webrev:http://j2se.east/deployment/www/webrevs/qz198522/6ux/6722527/install/ The test to verify the manifest is to run "sigcheck.exe -m filename"

EVALUATION For 6u7, there are 21 .exe's in the jre/bin directory: java-rmi.exe jureg.exe orbd.exe ssvagent.exe java.exe jusched.exe pack200.exe tnameserv.exe javacpl.exe keytool.exe policytool.exe unpack200.exe javaw.exe kinit.exe rmid.exe javaws.exe klist.exe rmiregistry.exe jucheck.exe ktab.exe servertool.exe Out of the 21 files, these 5 already have manifests: jureg.exe jusched.exe jucheck.exe javacpl.exe ssvagent.exe The following 16 files do not currently have manifests (broken into Deployment vs non-Deployment): 3 Owned by Deployment: pack200.exe unpack200.exe javaws.exe 13 Not owned by deployment: java-rmi.exe orbd.exe java.exe tnameserv.exe keytool.exe policytool.exe javaw.exe kinit.exe rmid.exe klist.exe rmiregistry.exe ktab.exe servertool.exe So the bulk of these files are part of the j2se ws, and are not owned by the Deployment team. I'm not sure if it's a good idea for Deployment engineers to be messing around with other teams Makefiles...and the Deployment team probably shouldn't be responsible for testing the other teams' binaries with their new manifests. So this might be a project that needs to be owned by several teams.