You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Herve Boutemy (JIRA)" <ji...@codehaus.org> on 2014/03/22 17:09:01 UTC

[jira] (MNG-5590) ${basedir} and ${project.basedir} do not behave the same on profile activation

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

Herve Boutemy updated MNG-5590:
-------------------------------

    Summary: ${basedir} and ${project.basedir} do not behave the same on profile activation  (was: ${basedir} and ${project.basedir} do not behave the same)

> ${basedir} and ${project.basedir} do not behave the same on profile activation
> ------------------------------------------------------------------------------
>
>                 Key: MNG-5590
>                 URL: https://jira.codehaus.org/browse/MNG-5590
>             Project: Maven 2 & 3
>          Issue Type: Bug
>    Affects Versions: 3.0.5, 3.1.1
>            Reporter: Henning Schmiedehausen
>            Assignee: Robert Scholte
>         Attachments: pom.xml
>
>
> According to http://maven.apache.org/ref/3.1.1/maven-model-builder/, the $\{basedir} property is deprecated and replaced by $\{project.basedir}. However the two are not the same. Consider the attached pom. 
> When using $\{basedir}/pom.xml in profile activation, running "help:active-profiles" will list 
>  - profile-test (source: pom)
> When using $\{project.basedir}/pom.xml, it will not list the profile as activated.
> It seems that the $\{project.<xxx>} properties get set after profile activation and evaluation (which makes sense because the profiles might affect these values), but profile activation requires them to be set before that has happened. 



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)