[ https://issues.apache.org/jira/browse/MWAR-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16554676#comment-16554676 ]
Nicolas Bihan commented on MWAR-418: ------------------------------------ Seems duplicate of https://issues.apache.org/jira/browse/MWAR-353 Issue is still there and prevents us to upgrade to version 3.x > Manifest not written to exploded location > ----------------------------------------- > > Key: MWAR-418 > URL: https://issues.apache.org/jira/browse/MWAR-418 > Project: Maven WAR Plugin > Issue Type: Bug > Components: manifest > Affects Versions: 3.2.2 > Reporter: Jeff Thomas > Priority: Major > > When creating the war with a configured archive/manifest the generated > MANIFEST only lands in the generated WAR but not in the exploded build-target > location. > If using WAR overlays the exploded location gets the MANIFEST.MF from the > overlay WAR and not the configured archive/manifest...even though the > documentation says that META-INF/MANIFEST.MF is automatically excluded. > Related Issue MWAR-167 was closed but the problem is not resolved. -- This message was sent by Atlassian JIRA (v7.6.3#76005)