You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benson Margulies (JIRA)" <ji...@codehaus.org> on 2010/08/15 14:35:32 UTC

[jira] Created: (MWAR-233) Please allow for MANIFEST.MF in exploded

Please allow for MANIFEST.MF in exploded
----------------------------------------

                 Key: MWAR-233
                 URL: http://jira.codehaus.org/browse/MWAR-233
             Project: Maven 2.x WAR Plugin
          Issue Type: New Feature
    Affects Versions: 2.1-beta-1
            Reporter: Benson Margulies


Since the MANIFEST.MF mechanism is taken from the archive plugin, and since there's no archiving going on with an exploded webapp, the exploded goal doesn't end up populating a manifest.

However, opening up the webapp MANIFEST.MF is a fairly common practice, and works just as well unpacked as packed -- if it is there. Thus, the exploded goal would be more useful if it could somehow borrow manifest generation even when no JAR is being created.


-- 
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

        

[jira] Closed: (MWAR-233) Please allow for MANIFEST.MF in exploded

Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MWAR-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephane Nicoll closed MWAR-233.
--------------------------------

    Resolution: Duplicate
      Assignee: Stephane Nicoll

See linked issue.

> Please allow for MANIFEST.MF in exploded
> ----------------------------------------
>
>                 Key: MWAR-233
>                 URL: http://jira.codehaus.org/browse/MWAR-233
>             Project: Maven 2.x WAR Plugin
>          Issue Type: New Feature
>    Affects Versions: 2.1-beta-1
>            Reporter: Benson Margulies
>            Assignee: Stephane Nicoll
>
> Since the MANIFEST.MF mechanism is taken from the archive plugin, and since there's no archiving going on with an exploded webapp, the exploded goal doesn't end up populating a manifest.
> However, opening up the webapp MANIFEST.MF is a fairly common practice, and works just as well unpacked as packed -- if it is there. Thus, the exploded goal would be more useful if it could somehow borrow manifest generation even when no JAR is being created.

-- 
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