You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Alix Warnke (JIRA)" <ji...@codehaus.org> on 2013/07/31 12:43:52 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:comment-tabpanel&focusedCommentId=329859#comment-329859 ] 

Alix Warnke commented on MWAR-167:
----------------------------------

Nothing has happened for three years. Could you please prioritize this issue? 
Currently we cannot see the revision number for web applications deployed from a development environment
                
> Final manifest not written to exploded location
> -----------------------------------------------
>
>                 Key: MWAR-167
>                 URL: https://jira.codehaus.org/browse/MWAR-167
>             Project: Maven 2.x WAR Plugin
>          Issue Type: Bug
>          Components: manifest
>    Affects Versions: 2.1-alpha-1
>            Reporter: Paul Benedict
>             Fix For: backlog
>
>         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, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira