You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Edd Steel (JIRA)" <ji...@codehaus.org> on 2008/09/05 16:57:48 UTC

[jira] Updated: (MASSEMBLY-332) MANIFEST.MF is not used when specified in configuration for a WAR format assembly

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

Edd Steel updated MASSEMBLY-332:
--------------------------------

    Attachment: MASSEMBLY-332-maven-assembly-plugin.patch

Attached patch that allows manifest creation for wars as well as jars. Among other things, this allows easy creation of skinny wars from fat wars.

> MANIFEST.MF is not used when specified in configuration for a WAR format assembly
> ---------------------------------------------------------------------------------
>
>                 Key: MASSEMBLY-332
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-332
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2-beta-2
>            Reporter: Julien Simon
>            Priority: Minor
>         Attachments: MASSEMBLY-332-maven-assembly-plugin.patch, maven_project.zip
>
>
> When you try to specify a manifestFile for an assembly with *war* format,  the manifest file specified is not used.
> I have attached a zip archive which contains a maven project that reproduces the bug. The assembly generated during the package phase and named myArtifactId-1.0.0-source.war contains a manifest file, but not the one specified in the maven-assembly-plugin  configuration in the pom.
> I tried different versions 2.1 and 2.2-beta-2 with jar and war assembly formats, here's the behavior description:
> maven-assembly *2.1* + *war* assembly format              >>>>>>> good manifest file included
> maven-assembly *2.2-beta-2* +*war* assembly format  >>>>>>> empty manifest file
> maven-assembly *2.1* + *jar* assembly format                 >>>>>>> good manifest file included
> maven-assembly *2.2-beta-2* + *jar* assembly format    >>>>>>> good manifest file included
>  
> The workaround is to use version 2.1 of the maven-assembly-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