This is a duplicate of Sun Bug #4991229, with some additional explanation for 1.4.2_05.

The "Invalid or corrupt jarfile" message is being reported for certain jar files in 1.4.2_05 due to the backport of the parse_manifest code from 1.5 to 1.4.2_05.  (It also reproduces in _06, by the way.)

In our specific case, it appears to be related to the Main-Class entry, which refers to the main class within our jar.  We execute this code thusly...

java -jar foo.jar <arglist>

Here's the manifest...

Manifest-Version: 1.0
Created-By: 9.0.5.10.66 (Oracle Corporation)
Oracle-IDE-Name: Oracle Ojc
Oracle-IDE-Version: 9.0.5.10.66
Main-Class: oracle.ojc.frontend.Main

Unfortunately, there is no documentation explaining the change, or explaining why these manifest entries should be invalid.  Until the _05 backport, this worked just fine.  But because of the backport, the code in question no longer functions properly on _05 or _06, or on the Mac (which uses _05 currently).

Please provide documentation on your site explaining this change in the 1.4.2 code base, and explaining why people's jar files aren't valid any longer.  If you query "invalid or corrupt jarfile" on Google, you'll see a lot of hits for this.  A lot of people have been encountering it.
###@###.### 2004-11-16 20:32:08 GMT