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 F3BC21818F for ; Tue, 8 Mar 2016 23:41:46 +0000 (UTC) Received: (qmail 7308 invoked by uid 500); 8 Mar 2016 23:41:41 -0000 Delivered-To: apmail-maven-issues-archive@maven.apache.org Received: (qmail 7179 invoked by uid 500); 8 Mar 2016 23:41:41 -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 7072 invoked by uid 99); 8 Mar 2016 23:41:41 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Mar 2016 23:41:41 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id DC9912C1F6D for ; Tue, 8 Mar 2016 23:41:40 +0000 (UTC) Date: Tue, 8 Mar 2016 23:41:40 +0000 (UTC) From: "Joerg Schaible (JIRA)" To: issues@maven.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (MWAR-367) Overlay removes /META-INF/context.xml MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MWAR-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186085#comment-15186085 ] Joerg Schaible commented on MWAR-367: ------------------------------------- Sorry, this is completely unacceptable! How can we now define default excludes in the pluginManagement of a parent that we want to use for all our overlays? Currently we simply add wars as dependency (we do this a lot) and can rely on proper defaults. Now, you force us to add for every dependent war an additional overlay section in the configuration of the war plugin. Sorry, this is simply insane! There have been arguments against this deprecation since *YEARS*! > Overlay removes /META-INF/context.xml > ------------------------------------- > > Key: MWAR-367 > URL: https://issues.apache.org/jira/browse/MWAR-367 > Project: Maven WAR Plugin > Issue Type: Bug > Components: overlay > Affects Versions: 2.6 > Reporter: Peter Rader > Assignee: Michael Osipov > Fix For: 3.0.0 > > Attachments: test.zip > > > A /src/main/webapp/META-INF/context.xml in a overlay could not be included. Even ${project.basedir}/target/war/work/myoverlaygroup/myoverlayartifact/META-INF/context.xml > is ignored. > Usually having copyXML=true, tomcat should copy the context.xml to /conf/Catalina/ but as long the xml is not part of the WAR i can not deploy on an virgin tomcat. -- This message was sent by Atlassian JIRA (v6.3.4#6332)