[
https://issues.apache.org/jira/browse/MASSEMBLY-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vlad Skarzhevskyy updated MASSEMBLY-768:
----------------------------------------
Attachment: pom.xml
mco.xml
> 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
> 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)
