[Closed] (MWAR-418) Manifest not written to exploded location

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[Closed] (MWAR-418) Manifest not written to exploded location

Michael Osipov (Jira)

     [ https://issues.apache.org/jira/browse/MWAR-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte closed MWAR-418.
-------------------------------
      Assignee: Robert Scholte
    Resolution: Duplicate

> 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
>            Assignee: Robert Scholte
>            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
(v8.3.4#803005)