You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tom (JIRA)" <ji...@codehaus.org> on 2009/11/29 15:29:55 UTC
[jira] Commented: (MWAR-213) Rename containerConfigXML if it does
not match context.xml
[ http://jira.codehaus.org/browse/MWAR-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199918#action_199918 ]
Tom commented on MWAR-213:
--------------------------
I can confirm this on:
* Apache Maven 2.2.1 (r801777; 2009-08-06 22:16:01+0300)
* Java version: 1.6.0_15
* OS name: "linux" version: "2.6.31-15-generic" arch: "amd64" Family: "unix"
Besides not working in profiles, it does not work in when put in build > plugins > plugin, too.
> 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
>
> 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