[ http://jira.codehaus.org/browse/MNG-2156?page=comments#action_61375 ]
Sachin Patel commented on MNG-2156:
-----------------------------------
The element works, the plugin documentation is incorrect and should be updated.
The manifestFile element needs to be specified under <archive> not under
<manifest>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<configuration>
<archive>
<manifestFile>META-INF/MANIFEST.MF</manifestFile>
</archive>
</configuration>
</plugin>
lowering severity
> maven-jar-plugin doesn't accept <manfiestFile> element in configuration
> -----------------------------------------------------------------------
>
> Key: MNG-2156
> URL: http://jira.codehaus.org/browse/MNG-2156
> Project: Maven 2
> Type: Bug
> Components: Plugins and Lifecycle
> Versions: 2.0.2
> Reporter: Sachin Patel
> Priority: Blocker
>
>
> The maven-jar-plugin does not accept the manfiestFile element in the
> configuration as advertised. The error reported is...
> [INFO] Failed to configure plugin parameters for:
> org.apache.maven.plugins:maven-jar-plugin:2.1-SNAPSHOT
> Cause: Cannot find setter nor field in
> org.apache.maven.archiver.ManifestConfiguration for 'manifestFile'
> Need to mark this as a blocker as their is no way to merge an existing
> MANFIEST that is needed to build an eclipse-plugin. The MANIFEST entries
> cannot be respecified in the plugin configuration because this would break
> running the plugin in a eclipse runtime-workbench. Keeping the manifest
> entires in the POM and in the MANIFEST file synchronized is too much
> maintainance. Need to support merging an existing manifest file.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
