[jira] [Commented] (MWAR-353) Manifest still not written to exploded location

["Robert Scholte (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MWAR-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16971816#comment-16971816 ] 

Robert Scholte commented on MWAR-353:
-------------------------------------

The code currently works like this: first create an exploded war ( as in {{war:exploded}} ), use this as input for the war ( as in {{war:war}} ).
The latter is responsible for adding files like MANIFEST.MF, pom.xml and pom.properties.
One solution would be to reverse this, so the exploded war looks exactly like the warfile, but that needs a huge rewrite, feeding the archiver with the right resources.


> Manifest still not written to exploded location
> -----------------------------------------------
>
>                 Key: MWAR-353
>                 URL: https://issues.apache.org/jira/browse/MWAR-353
>             Project: Maven WAR Plugin
>          Issue Type: Bug
>          Components: manifest
>    Affects Versions: 2.6
>            Reporter: Jakub Bochenski
>            Priority: Major
>             Fix For: 2.6
>
>
> If I have no manifest files I don't get anything in the exploded location.
> If I put a {{MANIFEST.MF}} under webapp folder's {{META-INF/MANIFEST.MF}} I just get the static file.
> If I set {{archive/manifestFile}} to point at some file I just get the static file.
> Workaround: change
> {code:xml}
> <goals> 
>   <goal>exploded</goal> 
> </goals>
> {code}
> to
> {code:xml}
> <goals> 
>   <goal>manifest</goal> 
>   <goal>exploded</goal> 
> </goals>
> {code}
>  
> and add the generated files to SCM ignore.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)