maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wisen Tanasa (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (MASSEMBLY-768) JarInputStream unable to find manifest created by version 2.5.4
Date Thu, 04 Feb 2016 12:08:39 GMT

    [ https://issues.apache.org/jira/browse/MASSEMBLY-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15132221#comment-15132221
] 

Wisen Tanasa edited comment on MASSEMBLY-768 at 2/4/16 12:07 PM:
-----------------------------------------------------------------

We are using 2.6 and this issue is not fixed in Linux. It however is working in Windows.

The entry ordering problem:
{code}
zipinfo.exe "foo.jar"
Zip file size: 80746 bytes, number of entries: 39
drwxr-xr-x  2.0 unx        0 b- stor 16-Feb-02 09:28 META-INF/
drwxr-xr-x  2.0 unx        0 b- stor 16-Feb-02 09:27 templates/
-rw-r--r--  2.0 unx     2380 bl defN 16-Feb-02 09:27 assembly.xml
-rw-r--r--  2.0 unx     3239 bl defN 16-Feb-02 09:27 templates/sts_custom_fields.txt
-rw-r--r--  2.0 unx      265 bl defN 16-Feb-02 09:28 META-INF/MANIFEST.MF
{code}

Reverted to 2.5.3 and the problem is fixed as well.

Shouldn't this bug be reopened?


was (Author: ceilfors):
We are using 2.6 and this issue is not fixed in Linux. It however is working in Windows.

The entry ordering problem:
{code}
zipinfo.exe "foo.jar"
Zip file size: 80746 bytes, number of entries: 39
drwxr-xr-x  2.0 unx        0 b- stor 16-Feb-02 09:28 META-INF/
-rw-r--r--  2.0 unx    15022 bl defN 16-Feb-02 09:27 templates/ATBExperianPreciseID.xml
drwxr-xr-x  2.0 unx        0 b- stor 16-Feb-02 09:27 templates/
-rw-r--r--  2.0 unx     2380 bl defN 16-Feb-02 09:27 assembly.xml
-rw-r--r--  2.0 unx     3239 bl defN 16-Feb-02 09:27 templates/sts_custom_fields.txt
-rw-r--r--  2.0 unx      265 bl defN 16-Feb-02 09:28 META-INF/MANIFEST.MF
{code}

Reverted to 2.5.3 and the problem is fixed as well.

Shouldn't this bug be reopened?

> JarInputStream unable to find  manifest created by version 2.5.4
> ----------------------------------------------------------------
>
>                 Key: MASSEMBLY-768
>                 URL: https://issues.apache.org/jira/browse/MASSEMBLY-768
>             Project: Maven Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.5.4
>         Environment: windows 64 bit, java 8. maven 3.3..3
>            Reporter: Vlad Skarzhevskyy
>            Assignee: Kristian Rosenvold
>            Priority: Critical
>             Fix For: 2.5.5
>
>         Attachments: mco.xml, pom.xml
>
>
> The problem is non trivial to reproduce. Changing back to version 2.5.3 resolves the
problem.
> On some computers plugin creates a jar file with manifest unreadable by java. JarInputStream
> see comments in JarInputStream(InputStream in, boolean verify)
> java expects manifest to be "either the first or the second entry in archive."
> looking at the gnerated jar using winrar generate report i see that in broken files MANIFEST.MF
 is not in right place.
> In example below it is third place.
> {noformat}
> #  Archive D:\sample-java\target\sample-bad.jar
> 2015-05-15 20:19        Folder        Folder  META-INF
> 2015-05-15 20:19        Folder        Folder  META-INF\lib
> 2015-05-15 20:19           274           203  META-INF\MANIFEST.MF
> 2015-05-14 01:43         10106          8342  META-INF\lib\mco2-sample-java-2.6.0-SNAPSHOT.jar
> 2015-03-04 15:46          8262          7790  mco2-sample-java.mco.png
> 2015-03-04 15:46         10400          1564  mco2-sample-java.mco.xml
> #
> # Total                   Size        Packed  Files
> #                        29042         17899  6
> {noformat}
> Please let me know if you need additional info. Or a complete test project.
> My assembly descriptor and partial pom with configuration will be attached



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message