[
http://jira.codehaus.org/browse/MWAR-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=231960#action_231960
]
Dennis Lundberg commented on MWAR-213:
--------------------------------------
Here's a suggestion for a work-around until this issues can be solved.
Put our context.xml files in different directories which all contains a file
named context.xml. So instead of doing
{code:xml}
<containerConfigXML>src/main/conf/remote-context.xml</containerConfigXML>
{code}
you'd do
{code:xml}
<containerConfigXML>src/main/conf-remote/context.xml</containerConfigXML>
{code}
> 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
