Created attachment 30113 [details] Use Java 5 to run this ant file for a demonstration Using ant 1.9.0 jar Java 5 fails to execute a jar file with the manifest attribute. Note: The generated jar works with Java 6 and 7. The problem is demonstrated when the manifest attribute is used with the jar task. I have attached a sample ant build.xml file to be used with Java 5 to view the failure.
The output using Java 5 is "Invalid or corrupt jarfile"
In addition you said on the mailing list, the problem went away if you used a nested manifest element inside the jar task instead, right? I'll look into it but may need your help testing it since I don't have any Java5 around anymore.
I have created AntUnit tests from your example - ine using a separate file and ine using a nested manifest - we'll see how they fare on our build matrix. I've compared the created jars byte by byte and the only difference is the timestamps. Right now I suspect Java5 cannot deal with the Zip64 extra field Ant 1.9 now adds, but then it should fail with nested manifest elements as well.
OK, both testcases fail in Jenkins, I'll add an option to completely turn of zip64 extensions and make turn it on in <jar> by default.
seems to be fixed with svn revision 1462911