Return-Path: X-Original-To: apmail-maven-issues-archive@minotaur.apache.org Delivered-To: apmail-maven-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4D78A177F3 for ; Mon, 18 May 2015 06:13:00 +0000 (UTC) Received: (qmail 27622 invoked by uid 500); 18 May 2015 06:13:00 -0000 Delivered-To: apmail-maven-issues-archive@maven.apache.org Received: (qmail 27568 invoked by uid 500); 18 May 2015 06:13:00 -0000 Mailing-List: contact issues-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@maven.apache.org Delivered-To: mailing list issues@maven.apache.org Received: (qmail 27557 invoked by uid 99); 18 May 2015 06:13:00 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 May 2015 06:13:00 +0000 Date: Mon, 18 May 2015 06:13:00 +0000 (UTC) From: "Kristian Rosenvold (JIRA)" To: issues@maven.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (MASSEMBLY-768) JarInputStream unable to find manifest created by version 2.5.4 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MASSEMBLY-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated MASSEMBLY-768: ----------------------------------------- Fix Version/s: 2.5.5 > 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)