[MNG-1775] No property expansion in profile activation

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.0, 2.0.1
• Component/s: Inheritance and Interpolation
• Environment: Linux
• Assignee: Benjamin Bentmann
• Reporter: Eric Andresen
• Created: 07/Dec/05 15:53
• Updated: 29/Mar/10 06:31
• Resolved: 29/Mar/10 06:31

Description

I have a profile specified in the pom.xml of a project. It is inteded to be activated based on the presence or absence of a file, using the <file> profile activator.

The profiles are simple:
<profile>
<id>metis</id>
<activation>
<file><missing>${basedir}/../build.properties</missing></file>
</activation>
<build>
<filters><filter>${basedir}/../build.properties.metis</filter></filters>
</build>
</profile>
<profile>
<id>dev</id>
<activation>
<file><exists>${basedir}/../build.properties</exists></file>
</activation>
<build>
<filters><filter>${basedir}/../build.properties</filter></filters>
</build>
</profile>

The problem comes in with ${basedir} – it isn't being expanded for purposes of evaluating the file. It's trying to look for a file named "${basedir}/../build.properties", rather than "/home/joe/projectX/projY/../build.properties"; as a result, the "missing" directive is always true, and the dev profile is never activated. When the filter path is evaluated, the ${basedir} property is evaluated, however.

Issue Links

• duplicates: MNG-2363 <profile><activation><file><exists/> does not work in a multi-project build
• duplicates: MNG-2809 Can't activate a profile by checking for the presence of a file in ${user.home}
• is duplicated by: MNG-2627 properties substitutions in exists