You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Rustam Abdullaev (JIRA)" <ji...@apache.org> on 2017/03/22 14:49:42 UTC

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

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

Rustam Abdullaev commented on MWAR-353:
---------------------------------------

The same applies to pom.xml and pom.properties. Those are not written to META-INF during war:exploded.

> 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
>             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
(v6.3.15#6346)