Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.1.0
-
None
-
OS: Windows XP Professional.
Java: 1.4.2_06
Maven: 2.1.0
Description
Next multimodule project structure is given:
/
--/parent/
------------pom.xml - this is aggregator which holds reference to child module in <modules> section.
------------profiles.xml - contains custom property "test.property=test-property-value".
--/child/
------------/src/main/resources/child.properties - contains property "some.useful.property=@test.property@". This property should be filtered using value defined - in profiles.xml.
------------/pom.xml - contains reference to parent/pom.xml in <parent> pom section.
So, when I run "mvn clean install" using parent/pom.xml I expect that in child/target/child.properties I will see filtered property "some.useful.property=test-property-value". But property remains unfiltered. src/main/resources in child/pom.xml are marjed as filtered.
Also, when I run the same command from "child" folder then property is filtered with right value. In single module build all works.
Maven 2.0.10 behaves in expected way and filters this property in both cases.
See attached test case.