You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Karl-Heinz Marbaise (JIRA)" <ji...@codehaus.org> on 2015/01/08 20:00:18 UTC
[jira] (MWAR-167) Final manifest not written to exploded location
[ https://jira.codehaus.org/browse/MWAR-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karl-Heinz Marbaise closed MWAR-167.
------------------------------------
Resolution: Fixed
Assignee: Karl-Heinz Marbaise
Fixed in [r1650354|http://svn.apache.org/r1650354]
Patch applied with slight modifications.
> Final manifest not written to exploded location
> -----------------------------------------------
>
> Key: MWAR-167
> URL: https://jira.codehaus.org/browse/MWAR-167
> Project: Maven WAR Plugin
> Issue Type: Bug
> Components: manifest
> Affects Versions: 2.1-alpha-1
> Reporter: Paul Benedict
> Assignee: Karl-Heinz Marbaise
> Fix For: 2.6
>
> 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 was sent by Atlassian JIRA
(v6.1.6#6162)