You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dennis Lundberg (JIRA)" <ji...@codehaus.org> on 2006/07/12 00:31:22 UTC
[jira] Updated: (MJAR-46) Document element in
configuration
[ http://jira.codehaus.org/browse/MJAR-46?page=all ]
Dennis Lundberg updated MJAR-46:
--------------------------------
Summary: Document <manifestFile> element in configuration (was: Document <manfiestFile> element in configuration)
> Document <manifestFile> element in configuration
> ------------------------------------------------
>
> Key: MJAR-46
> URL: http://jira.codehaus.org/browse/MJAR-46
> Project: Maven 2.x Jar Plugin
> Type: Improvement
> Versions: 2.0
> Reporter: Sachin Patel
> Priority: Minor
> Fix For: 2.1
>
>
> 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