[
http://jira.codehaus.org/browse/MWAR-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephane Nicoll updated MWAR-142:
---------------------------------
Component/s: overlay
> 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: 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
