[
http://jira.codehaus.org/browse/MWAR-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=231744#action_231744
]
Dennis Lundberg commented on MWAR-167:
--------------------------------------
@Paul
Is this releated to MWAR-197.
@Haikal
If you are using another plugin to generate a custom manifest that you include
in the WAR Plugin's configuration, then you need to execute that plugin
*before* the war or exploded goal. Something like this:
mvn manifest:create-custom war:war
> 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: mvn167-with-it.diff, 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
