You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Olivier Lamy (JIRA)" <ji...@codehaus.org> on 2008/02/17 23:41:28 UTC

[jira] Updated: (MWAR-31) Support needed to allow use of custom manifest file

     [ http://jira.codehaus.org/browse/MWAR-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivier Lamy updated MWAR-31:
-----------------------------

         Assignee: Olivier Lamy
    Fix Version/s: 2.1

> Support needed to allow use of custom manifest file
> ---------------------------------------------------
>
>                 Key: MWAR-31
>                 URL: http://jira.codehaus.org/browse/MWAR-31
>             Project: Maven 2.x War Plugin
>          Issue Type: Improvement
>            Reporter: Mang Lau
>            Assignee: Olivier Lamy
>            Priority: Minor
>             Fix For: 2.1
>
>
> Related to [MPWAR-22|http://jira.codehaus.org/browse/MPWAR-22] that was fixed for Maven 1 and is not present in Maven 2.  We should be able to specify the path to our own custom manifest file when building a war, just like the <manifestFile> tag in the maven-ear-plugin.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira