maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl-Heinz Marbaise (JIRA)" <j...@codehaus.org>
Subject [jira] (MWAR-167) Final manifest not written to exploded location
Date Thu, 08 Jan 2015 19:24:18 GMT

    [ https://jira.codehaus.org/browse/MWAR-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=360974#comment-360974
] 

Karl-Heinz Marbaise edited comment on MWAR-167 at 1/8/15 1:23 PM:
------------------------------------------------------------------

Fixed in [r1650354|http://svn.apache.org/r1650354]
Patch applied with slight modifications.
Followup in [r1650356|http://svn.apache.org/r1650356]
Added missing exclusion for MANIFEST.MF file for apache-rat-plugin.


was (Author: khmarbaise):
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)

Mime
View raw message