Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 183035 - update jar signer on build.eclipse.org to use latest version of jarprocessor
Summary: update jar signer on build.eclipse.org to use latest version of jarprocessor
Status: RESOLVED FIXED
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: Servers (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Eclipse Webmaster CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-18 14:59 EDT by Kim Moir CLA
Modified: 2007-04-19 13:55 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kim Moir CLA 2007-04-18 14:59:14 EDT 
Andrew has created a standalone jar processor that is available with each of our builds.  Also, he fixed many jar processor bugs.  

This bug is a request to update to the latest version of the jar processor on build.eclipse.org used during the signing process.

This is the latest

http://www.eclipse.org/downloads/download.php?file=/eclipse/downloads/drops/I20070417-0800/jarprocessor.jar

See bug 178886 for more information.

It would be great if this could be updated before M7, which starts April 27.
Comment 1 Denis Roy CLA 2007-04-18 16:47:04 EDT 
Do I just plop the new file over the old one, or do I need to change the parameters at all?
Comment 2 Andrew Niefer CLA 2007-04-18 16:55:09 EDT 
You can just drop the new one on top of the old one.
Comment 3 Denis Roy CLA 2007-04-19 13:55:31 EDT 
I updated jarprocessor.jar.  I tested signing a JAR, and it seems to have been successful according to jarsigner -verify -verbose.