zip64 compatibility problems (original) (raw)

Kumar Srinivasan kumar.x.srinivasan at oracle.com
Wed Jan 16 15:35:37 UTC 2013

On 1/16/2013 4:20 AM, Alan Bateman wrote:

On 16/01/2013 03:40, Martin Buchholz wrote:

:

It's a different story for the groups of users just now adopting jdk7. The situation is a bit grim for those using jar files with>64k entries. jdk7 is not only creating jar files that are unreadable by jdk6 - they are also unreadable by the jdk7 launcher! With no visible benefit for the user! Just to be clear, do you mean just executable JAR files (java -jar)? I assume that library JAR files on the classpath or elsewhere with >64k are not an issue. Only -jar would be affected since the launcher needs to read the manifest to extract the main-class name, so the changeset which Martin refers to, fixes the parse_manifest.c. Therefore using the construct java -cp foo.jar Main .... would/should work correctly via the classloader.

Kumar

-Alan

More information about the core-libs-dev mailing list