[
http://jira.codehaus.org/browse/MWAR-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=231860#action_231860
]
Dennis Lundberg commented on MWAR-213:
--------------------------------------
Having thought some more about this, isn't "context.xml" a Tomcat specific
name. IIRC there is no such thing in the Servlet spec. So the name of the file
is different for different Servlet Containers. To accommodate your request we
would need another parameter "containerConfigXMLOutputName", that can be set to
"context.xml" for Tomcat specific projects. The default value should be to use
the same name as the input, i.e. the current behavior.
> Rename containerConfigXML if it does not match context.xml
> ----------------------------------------------------------
>
> Key: MWAR-213
> URL: http://jira.codehaus.org/browse/MWAR-213
> Project: Maven 2.x WAR Plugin
> Issue Type: Improvement
> Affects Versions: 2.1-beta-1
> Environment: Maven 2.0.10, JDK6, XP SP3
> Reporter: Michael Osipov
> Priority: Critical
> Attachments: MWAR-213.zip
>
>
> I ran into some problems with this plugin in use with profiles. I deploy
> different context.xml files. So I made up some names like:
> remote-context.xml and set
> <containerConfigXML>src/main/conf/remote-context.xml
> </containerConfigXML> but when I run the package phase the file is copied as
> is and is not renamed to context.xml. Which of course makes no sense without
> renaming.
> Files should be renamed if necessary.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
