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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.5, 3.1.1, 3.2.1
• Fix Version/s: 3.2.2
• Assignee: Herve Boutemy
• Reporter: Henning Schmiedehausen
• Created: 14/Feb/14 22:23
• Updated: 30/Aug/23 16:48
• Resolved: 23/Mar/14 10:38

Description

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.

Issue Links

• duplicates: MNG-5516 ${project.basedir} in profile activation exists clause strange behavior
• relates to: MNG-5608 warn if file-based profile activation uses ${project.basedir} since only ${basedir} is supported