You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Martin Buechler (JIRA)" <ji...@codehaus.org> on 2008/11/05 21:56:51 UTC

[jira] Closed: (MNG-3817) Property inheritance when filtering with multiple profiles is gone

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

Martin Buechler closed MNG-3817.
--------------------------------

       Resolution: Not A Bug
    Fix Version/s: 2.0.9

The problem exists only if empty values are inherited, which can be quite always eliminated by avoiding to rely on empty values.

> Property inheritance when filtering with multiple profiles is gone 
> -------------------------------------------------------------------
>
>                 Key: MNG-3817
>                 URL: http://jira.codehaus.org/browse/MNG-3817
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Profiles
>    Affects Versions: 2.0.9
>            Reporter: Martin Buechler
>            Priority: Blocker
>             Fix For: 2.0.9
>
>         Attachments: MNG-3817.zip
>
>
> pom.xml:
> <build>
>        <filters>                    
>              <filter>default.properties</filter>
>          </filters>
> </build>
> <profiles>	
> 	<profile>
>             <id>first</id>
>             <build>
>                 <filters>                    
>                     <filter>first.properties</filter>
>                 </filters>
>             </build>
>         </profile>
> 	 <profile>
>             <id>second</id>
>             <build>
>                 <filters>                    
>                     <filter>second.properties</filter>
>                 </filters>
>             </build>
> ...
> default.properties:
> prop=
> first.properties:
> prop=first_value
> second.properties:
> other_prop=${prop}
> since 2.0.9 the value of 
>     other_prop 
> is not replaced and is written as ${prop}, instead of inherit the value 'first_value', when executing
>    mvn -Pfirst,second process-resources
> This breaks existing configurations badly and I do not see a workaround whithout losing the ability to configure in more than one dimension, which makes mvn 2.0.9 quite unsuable for project requirements in real life.
> 	

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