[
https://jira.codehaus.org/browse/MNG-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNG-5590:
-------------------------------
Fix Version/s: 3.0.6
> ${basedir} and ${project.basedir} do not behave the same on file-based
> profile activation
> -----------------------------------------------------------------------------------------
>
> Key: MNG-5590
> URL: https://jira.codehaus.org/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
> Fix 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
(v6.1.6#6162)
