[
https://issues.apache.org/jira/browse/MJAR-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MJAR-195.
------------------------------------
Resolution: Not A Problem
Assignee: Karl Heinz Marbaise
This can be achieved by using [the
following|http://maven.apache.org/shared/maven-archiver/examples/manifestFile.html]:
{code:xml}
<project>
...
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
...
<configuration>
<archive>
<manifestFile>src/main/resources/META-INF/MANIFEST.MF</manifestFile>
</archive>
</configuration>
...
</plugin>
</plugins>
</build>
...
</project>
{code}
> 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
>
> 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)
