[ https://issues.apache.org/jira/browse/MWAR-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16356958#comment-16356958 ]
Jakub Bochenski commented on MWAR-353: -------------------------------------- {quote}Workaround doesn't work with 3.1.0 as manifest goal was removed{quote} [~khmarbaise] any chance you could post the "MavenArchiver configuration" that can be used to replace the lost functionality? > 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 (v7.6.3#76005)