[
https://issues.apache.org/jira/browse/MJAR-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14573713#comment-14573713
]
Karl Heinz Marbaise commented on MJAR-195:
------------------------------------------
The shuffling is a point but this seemed to be only a beauty kind of issue.
Furthermore there are entries which are added by default (see the oracle JDK
docs for MANIFEST.MF files). Apart from that A manifest.mf file is handled with
property like entries which are addressed by keys where there order doesn't
matter. So i don't really see the problem? Except from a optical point of view?
If you need to stock with Maven 3.0.5 why not downloading a newer version ...
> 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)
