[
https://issues.apache.org/jira/browse/MJAR-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14573727#comment-14573727
]
Amichai Rothman commented on MJAR-195:
--------------------------------------
You're right, I should refer to the jar plugin version explicitly.
Adding <version>2.4</version> or <version>2.6</version> to the jar plugin
configuration in this test project still results in the same issue.
Specifically, this is the manifest I see in target/mftest-1.jar:
Manifest-Version: 1.0
A-entry: first
D-entry: fourth
Built-By: amichai
Build-Jdk: 1.7.0_80
E-entry: fifth
B-entry: second
Created-By: me
C-entry: third
Archiver-Version: Plexus Archiver
...which is not the unmodified existing manifest file.
Are you seeing a different result when you run the test project?
> Add option to use unmodified existing manifest file
> ---------------------------------------------------
>
> Key: MJAR-195
> URL: https://issues.apache.org/jira/browse/MJAR-195
> Project: Maven JAR Plugin
> Issue Type: Bug
> Affects Versions: 2.6
> Reporter: Amichai Rothman
> Assignee: Karl Heinz Marbaise
> Attachments: mftest.tgz
>
>
> Currently, the jar plugin performs various manipulations on the manifest
> file, such as adding some entries and shuffling their order, and lacks
> functionality such as removing entries (there are separate issues for those).
> The workaround for these should be the ability to use an existing manifest
> file, whether hand-crafted or generated by other means such as ant, however
> the jar plugin seems to always modify the manifest just before adding it to
> the jar, thus preventing any such workaround from working.
> Please add a configuration option that causes the jar plugin to simply use an
> existing manifest file (e.g. one specified via manifestFile) without
> modifying it in any way - just copying it as-is into the generated jar file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
