Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 132046

Summary:	Change JAR signing script to allow specification of output file
Product:	Community	Reporter:	John Arthorne <john.arthorne>
Component:	Cross-Project	Assignee:	Cross-Project issues <cross-project.inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	sonia_dimitrov, webmaster
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows 2000
Whiteboard:

Description John Arthorne

2006-03-15 18:11:06 EST

There is currently no reliable way to figure out when the JAR signing script has completed.  If the script allowed the caller to specify an output file, it could create that output file after signing.  Then the build process that is calling the script can determine when the signing is complete by checking for existence of the output file.

Comment 1 John Arthorne

2006-04-05 10:44:29 EDT

Moving to Callisto component.

To be clear, this refers to the /usr/bin/sign script that adds items to the signing queue.

Comment 2 Eclipse Webmaster

2006-04-20 17:02:03 EDT

Done.

$> sign
Usage: /usr/bin/sign <file> <mail|nomail> [outputDir]
Signs JAR or ZIP file <file>, placing the resulting file in optional [outputDir] and mails notification that signing is complete, if requested

outputDir can be relative or absolute to the signed file. If not specified, the current directory is implied.  If outputDir does not exist, it will be created automatically.

Closing as FIXED.  Feel free to reopen if something breaks.

D.