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

["Hudson (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MNG-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17069512#comment-17069512 ] 

Hudson commented on MNG-5590:
-----------------------------

Build failed in Jenkins: Maven TLP » maven-studies » maven-metrics #4

See https://builds.apache.org/job/maven-box/job/maven-studies/job/maven-metrics/4/

> ${basedir} and ${project.basedir} do not behave the same on file-based profile activation
> -----------------------------------------------------------------------------------------
>
>                 Key: MNG-5590
>                 URL: https://issues.apache.org/jira/browse/MNG-5590
>             Project: Maven
>          Issue Type: Bug
>    Affects Versions: 3.0.5, 3.1.1, 3.2.1
>            Reporter: Henning Schmiedehausen
>            Assignee: Herve Boutemy
>            Priority: Major
>             Fix For: issues to be reviewed for 3.0.6, 3.2.2
>
>         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
(v8.3.4#803005)