You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2008/11/13 17:39:13 UTC
[jira] Commented: (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:comment-tabpanel&focusedCommentId=154094#action_154094 ]
Benjamin Bentmann commented on MNG-3817:
----------------------------------------
Clarification:
Maven versions before 2.0.9 do *not* provide default versions for the plugins, this is a new feature introduced in Maven 2.0.9 (MNG-3395). Previously, you just got LATEST for any plugin whose version was not explicitly specified. LATEST being quite subject to time and other environmental aspects, this is a suboptimal choice for anybody seeking reproducible builds.
Moral:
Always specify the desired version for each and every plugin your build uses.
> 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