Despite the fact that it is possible to generate a custom manifest as described in war-manifest-guide, 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).
|Component/s||overlay [ 14514 ]|
|Component/s||manifest [ 14515 ]|
|Assignee||Olivier Lamy [ olamy ]|
|Resolution||Not A Bug [ 6 ]|
|Status||Open [ 1 ]||Closed [ 6 ]|
|Project Import||Sun Apr 05 13:28:45 UTC 2015 [ 1428240525159 ]|
|Workflow||jira [ 12728556 ]||Default workflow, editable Closed status [ 12764899 ]|
|Project Import||Mon Apr 06 01:49:55 UTC 2015 [ 1428284995525 ]|
|Workflow||jira [ 12966467 ]||Default workflow, editable Closed status [ 13002823 ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|1969d 21h 30m||1||Olivier Lamy (*$^¨%`£)||01/Jul/13 08:51|