You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Gabriela Chiribau (JIRA)" <ji...@codehaus.org> on 2011/04/12 14:54:22 UTC

[jira] Commented: (MWAR-142) custom manifest and war overlays

    [ http://jira.codehaus.org/browse/MWAR-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=263281#action_263281 ] 

Gabriela Chiribau commented on MWAR-142:
----------------------------------------

It is useful to have the ability to keep one's own manifest, especially when using maven to generate a war file for "other" application servers. E.g websphere doesn't accept the manifest generated by maven, it required \n instead of space as the separator the manifest. The ability to specify an existing manifest just to have it overriden is somewhat frustrating :)

Also, the classpath is overriden in the manifest with or _without_ addClasspath=false; this is plainly ignored.

					<archive>
						<manifestFile>
							WebContent/META-INF/MANIFEST.MF
                 		</manifestFile>
                 		<manifest>
                 			<addClasspath>false</addClasspath>
                 			
                 		</manifest>
			</archive>

This will still override the manifest _with_ the classpath generated by maven.

> custom manifest and war overlays
> --------------------------------
>
>                 Key: MWAR-142
>                 URL: http://jira.codehaus.org/browse/MWAR-142
>             Project: Maven 2.x WAR Plugin
>          Issue Type: Improvement
>          Components: manifest, overlay
>    Affects Versions: 2.0.2, 2.1-alpha-1
>         Environment: maven 2.0.7
>            Reporter: Rémy Sanlaville
>         Attachments: custom-manifest-war-overlays.zip
>
>
> Despite the fact that it is possible to generate a custom manifest as described in [war-manifest-guide|http://maven.apache.org/plugins/maven-war-plugin/examples/war-manifest-guide.html], it's not good enough when using the overlays mechanism. The maven-war-plugin can't take into account an existing manifest. It can just generate a new one with the corresponding configuration in the pom.
> However, if you use the overlays mechanism, you rather want to keep the manifest from your common war (see custom-manifest-war-overlays.zip in attachment). 

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