You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "denis dudinski (JIRA)" <ji...@codehaus.org> on 2009/04/09 10:00:19 UTC

[jira] Updated: (MNG-4126) Properties defined in profiles.xml are not used during multimodule build when filtering resources in modules.

     [ http://jira.codehaus.org/browse/MNG-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

denis dudinski updated MNG-4126:
--------------------------------

    Attachment: DefaultMavenProjectBuilder.patch

Patch that fixes mentioned problem.

> Properties defined in profiles.xml are not used during multimodule build when filtering resources in modules.
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-4126
>                 URL: http://jira.codehaus.org/browse/MNG-4126
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Inheritance and Interpolation, Profiles
>    Affects Versions: 2.1.0
>         Environment: OS: Windows XP Professional.
> Java: 1.4.2_06
> Maven: 2.1.0
>            Reporter: denis dudinski
>         Attachments: DefaultMavenProjectBuilder.patch, profiles-xml-it.zip
>
>
> 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.

-- 
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