[JBoss JIRA] Closed: (NETTY-361) jar file construction is not compatible with the jar file format produced by sun's jar tools

[Trustin Lee (JIRA)]

     [ https://issues.jboss.org/browse/NETTY-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Trustin Lee closed NETTY-361.
-----------------------------

    Resolution: Done


Marking as a duplicate of NETTY-376 (because it has better explanation)

> jar file construction is not compatible with the jar file format produced by sun's jar tools
> --------------------------------------------------------------------------------------------
>
>                 Key: NETTY-361
>                 URL: https://issues.jboss.org/browse/NETTY-361
>             Project: Netty
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 3.2.3.Final
>         Environment: linux 2.6.18-92.1.22.el5.centos.plus SMP; oracle/sun java 1.6.0_18
>            Reporter: jdefelice
>            Assignee: Trustin Lee
>             Fix For: 3.2.4.Final
>
>
> Loading the netty-3.2.3-Final.jar file via JarInputStream results in a NULL manifest when getManifest() is invoked on the stream.  This is a result of the file ordering within the jar file and the method by which JarInputStream uses to read manifest files: it assumes that the first entry in the jar is META-INF/ and the second entry is META-INF/MANIFEST.MF.  Oracle/Sun's jar tool correctly enforces this structure.  I use about a dozen other jars in my project, none of which suffer this same problem - netty is the only one.
> This issue has been logged against Oracle/Sun's database : http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4338238
> It seems that it's up to the jar file provider to make sure that jar files are produced according to these undocumented requirements.
> It's easy to see the location of the manifest within the jar file: on my system I ran 'unzip -l netty-3.2.3-Final.jar' and it is quite clear that the META-INF/MANIFEST.MF file is NOT the second entry in the stream.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira