From issues-return-85936-apmail-maven-issues-archive=maven.apache.org@maven.apache.org Mon Jul 1 12:53:34 2013 Return-Path: X-Original-To: apmail-maven-issues-archive@minotaur.apache.org Delivered-To: apmail-maven-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1CB8010A28 for ; Mon, 1 Jul 2013 12:53:34 +0000 (UTC) Received: (qmail 9688 invoked by uid 500); 1 Jul 2013 12:53:33 -0000 Delivered-To: apmail-maven-issues-archive@maven.apache.org Received: (qmail 9632 invoked by uid 500); 1 Jul 2013 12:53:32 -0000 Mailing-List: contact issues-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@maven.apache.org Delivered-To: mailing list issues@maven.apache.org Received: (qmail 9620 invoked by uid 99); 1 Jul 2013 12:53:31 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Jul 2013 12:53:31 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [199.193.192.100] (HELO codehaus01.managed.contegix.com) (199.193.192.100) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Jul 2013 12:53:26 +0000 Received: from codehaus01 (localhost.localdomain [127.0.0.1]) by codehaus01.managed.contegix.com (Postfix) with ESMTP id 2732FB10B2 for ; Mon, 1 Jul 2013 07:53:06 -0500 (CDT) Date: Mon, 1 Jul 2013 07:53:06 -0500 (CDT) From: "Olivier Lamy (JIRA)" To: issues@maven.apache.org Message-ID: In-Reply-To: References: Subject: [jira] (MWAR-142) custom manifest and war overlays MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 22cf62d5d84cf5bea94eb3b65e0ebd09 X-Virus-Checked: Checked by ClamAV on apache.org [ https://jira.codehaus.org/browse/MWAR-142?page=3Dcom.atlassian.jira.= plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MWAR-142. ----------------------------- Resolution: Not A Bug Assignee: Olivier Lamy close issue as requested by reporter. =20 > custom manifest and war overlays > -------------------------------- > > Key: MWAR-142 > URL: https://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=E9my Sanlaville > Assignee: Olivier Lamy > Attachments: custom-manifest-war-overlays.zip > > > Despite the fact that it is possible to generate a custom manifest as des= cribed in [war-manifest-guide|http://maven.apache.org/plugins/maven-war-plu= gin/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 existin= g manifest. It can just generate a new one with the corresponding configura= tion in the pom. > However, if you use the overlays mechanism, you rather want to keep the m= anifest from your common war (see custom-manifest-war-overlays.zip in attac= hment).=20 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs For more information on JIRA, see: http://www.atlassian.com/software/jira