[
http://jira.codehaus.org/browse/MWAR-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=187442#action_187442
]
Haikal Saadh edited comment on MWAR-167 at 8/17/09 11:12 PM:
-------------------------------------------------------------
Here's a patch that copies a user specified manifest to the correct place when
you do war:exploded.
First time working on a maven plugin, so go easy :D
patch is against /tags/maven-war-plugin-2.1-beta-1
was (Author: tunaranch):
Here's a patch that copies a user specified manifest to the correct place
when you do war:exploded.
First time working on a maven plugin, so go easy :D
> Final manifest not written to exploded location
> -----------------------------------------------
>
> Key: MWAR-167
> URL: http://jira.codehaus.org/browse/MWAR-167
> Project: Maven 2.x WAR Plugin
> Issue Type: Bug
> Affects Versions: 2.1-alpha-1
> Reporter: Paul Benedict
> Priority: Minor
> Attachments: patch.diff
>
>
> When I open up my generated WAR file, the Manifest file contains all the
> entries I specified. This is correct. However, when I look into the exploded
> location, it's just the file I had in my project to begin with.
> The exploded Manifest should be updated with the final contents.
--
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
