Richard Eggert created MWAR-307:
-----------------------------------
Summary: containerConfigXML exhibits Tomcat-specific behavior
Key: MWAR-307
URL: https://jira.codehaus.org/browse/MWAR-307
Project: Maven WAR Plugin
Issue Type: Bug
Affects Versions: 2.4
Reporter: Richard Eggert
The containerConfigXML configuration parameter allows the user to specify a
container-specific deployment descriptor file (context.xml, jboss-web.xml,
jetty-web.xml, sun-web.xml, weblogic.xml, etc.) to include in the WAR. The
plugin places this file in the WAR file's META-INF directory.
However, expecting the file in this location is behavior unique to Tomcat.
Every other webapp container in the universe (and possibly parallel universes -
I can't be too sure) expects the container-specific deployment descriptor to be
located in WEB-INF (alongside web.xml), though some containers are flexible in
this regard.
The current plugin behavior makes this configuration parameter unusable when
packaging for any container other than Tomcat, forcing users to configure the
file as a "webResource" instead.
The location within the WAR where the container-specific deployment descriptor
is placed ought to be configurable. I would even say that WEB-INF should be the
default, since that is where every container except Tomcat expects it to be
(and is where it logically should be, since that is where web.xml goes), but
that would unfortunately break it for projects that already rely on the current
behavior.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
