Tested_Java_Release : "1.5.0-beta2
build/bundles : 1.5.0-beta2-b42"
Tested_Java_Location :
/net/koori/onestop/jdk/1.5.0/latest/bundles
Tested_Machine_Name : dnm-011/jitender/dnm-101/dnm-dtf-016
Tested O/S : winxp/win2k/solars9/RHADS3.0

Problem description :
pack200 -r new.jar test.jar, should produce a new.jar file from test.jar,by packing and unpacking the test.jar. This resulting test.jar can be used by the users as a input to jarsigner. But the resulting new.jar is somehow corrupted.

Steps to reproduce
------------------
1)<jdk_home>/pack200 -r new.jar test.jar
2) Try to do unzip -t or jar -tvf against test.jar,it will display all the contents of the test.jar.
3) Now try to unzip-t against new.jar(pack-unpacked file),it will display following
Archive: new.jar
  End-of-central-directory signature not found. Either this file is not
  a zipfile, or it constitutes one disk of a multi-part archive. In the
  latter case the central directory and zipfile comment will be found on
  the last disk(s) of this archive.
unzip: cannot find zipfile directory in one of new.jar or
        new.jar.zip, and cannot find new.jar.ZIP, period.

4) jar -tvf new.jar will return nothing

If you are able to reproduce the above mentioned scenarios then the bug is reporduced

Also it has been noticed that it's creating two extra file "stdout" and "new.jar-orig.jar"