Bug 193568 - [JarProcessor] Need tool to verify pack.gz files
Summary: [JarProcessor] Need tool to verify pack.gz files
Status: RESOLVED FIXED
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: p2 (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.4   Edit
Assignee: Andrew Niefer CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks: 240855
  Show dependency tree
 
Reported: 2007-06-20 12:43 EDT by Andrew Niefer CLA
Modified: 2009-02-20 12:12 EST (History)
3 users (show)

See Also:

Attachments
initial implementation (8.07 KB, patch)
2007-06-20 12:49 EDT, Andrew Niefer CLA 		no flags Details | Diff
jarprocessor.jar (40.58 KB, application/octet-stream)
2007-06-20 12:51 EDT, Andrew Niefer CLA 		no flags Details
View All 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 Andrew Niefer CLA 2007-06-20 12:43:44 EDT 
There still exists some issues with some jars failing to verify after pack/unpack (see for example bug 192983).
We need a tool that can be used to verify that a set of pack.gz files will unpack and verify properly.
Comment 1 Andrew Niefer CLA 2007-06-20 12:49:08 EDT 
Created attachment 71927 [details]
initial implementation
Comment 2 Andrew Niefer CLA 2007-06-20 12:51:53 EDT 
Created attachment 71930 [details]
jarprocessor.jar

jarprocessor.jar containing attached changes.

Run with:
java -cp jarprocessor.jar org.eclipse.update.internal.jarprocessor.verifier.Verifier -dir <workingDir> <input>

Run with a jdk that has a jarsigner, or have jarsigner on your path.
Input is a directory or a pack.gz file.  Each pack.gz file will be unpacked under the workingDir then verified with jarsigner.

If no arguments are given, the current directory is the input and the workingDir will be a jarprocessor.verifier.temp directory.
Comment 3 DJ Houghton CLA 2008-07-08 16:05:09 EDT 
Marking as 3.5 target so we don't lose track of this. Andrew, didn't we have another bug open about adding something like this to the releng tests to verify the build? I can't seem to find it right now...
Comment 4 Andrew Niefer CLA 2009-02-20 12:12:20 EST 
I'm going to call this fixed, 3.4 contains that initial implementation.

See also bug 252869