You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Roy Arnon (JIRA)" <ji...@apache.org> on 2017/07/24 14:17:00 UTC

[jira] [Created] (MJAR-239) Class-Path order has changed is incorrect when adding ManifestEntries

Roy Arnon created MJAR-239:
------------------------------

             Summary: Class-Path order has changed is incorrect when adding ManifestEntries
                 Key: MJAR-239
                 URL: https://issues.apache.org/jira/browse/MJAR-239
             Project: Maven JAR Plugin
          Issue Type: Bug
    Affects Versions: 3.0.2
            Reporter: Roy Arnon
         Attachments: MANIFEST-end.MF, MANIFEST-start.MF, test_case.zip

It seems that in maven-jar-plugin 3.0.2 - that uses maven-archiver-3.11, which is where I think the bug is - the order of the added Class-Path entries in manifest file has changed between 3.0.1 (which added them to start of entries) and 3.0.2 (which adds them to bottom).

I have attached a minimal test case to display this issue.
There are 2 pom files - pom.xml generates the manifest with the entries at start, and pom-old.xml generates the manifest with the entries at the end.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)