Henning Schmiedehausen created MNG-5590:
-------------------------------------------
Summary: ${basedir} and ${project.basedir} do not behave the same
Key: MNG-5590
URL: https://jira.codehaus.org/browse/MNG-5590
Project: Maven 2 & 3
Issue Type: Bug
Affects Versions: 3.1.1, 3.0.5
Reporter: Henning Schmiedehausen
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)
