profiles.xml does not always override pom.xml, at least when using sub-modules
------------------------------------------------------------------------------
Key: MNG-3287
URL: http://jira.codehaus.org/browse/MNG-3287
Project: Maven 2
Issue Type: Bug
Components: Inheritance and Interpolation, Profiles
Affects Versions: 2.0.7
Reporter: Boris Maras
Attachments: TestInheritance.zip
I have attached a test case to reproduce the problem. It has to be launched
with profile "dev".
I have a master pom.xml and a child pom.xml
In the master pom.xml is defined a profile "dev", with a property set to the
value "dev_pom.xml".
In the child pom.xml, I display the value of the property with the ant plugin.
There is also a file profiles.xml that overrides the property of the profile,
with the value "dev_profiles.xml".
If you run "mvn install -Pdev" on the child module, it displays
"dev_profiles.xml".
If you run "mvn antrun:run -Pdev" on the child module, it also displays
"dev_profiles.xml".
But if you run "mvn install -Pdev" on the master module, it displays
"dev_pom.xml".
It looks like the child module uses the value defined in the master pom, and
ignores the fact that it has been overriden by profiles.xml. And this behavior
occurs only if this child module is called through the master pom.
Moreover, if you remove the value in the master pom, then the child pom is able
to find the value in profiles.xml.
--
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
