maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joerg Schaible (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MWAR-367) Overlay removes /META-INF/context.xml
Date Tue, 08 Mar 2016 23:41:40 GMT

    [ 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 <containerConfigXML>${project.basedir}/target/war/work/myoverlaygroup/myoverlayartifact/META-INF/context.xml</containerConfigXML>

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

Mime
View raw message