[
https://issues.apache.org/jira/browse/MJAR-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17832446#comment-17832446
]
Slawomir Jaranowski commented on MJAR-239:
------------------------------------------
Was fixed probably in {{3.1.2}}
{code:java}
Class-Path: /foo /lib/junit-4.12.jar /lib/hamcrest-core-1.3.jar {code}
The same is for master version.
We can add a *IT* for such cases.
> 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
> Priority: Major
> Fix For: waiting-for-feedback
>
> 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
(v8.20.10#820010)
