[MANTTASKS-179] Variables nested in pom.xml are not being interpolated

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1.0
• Fix Version/s: 2.1.1
• Component/s: pom task
• Assignee: Herve Boutemy
• Reporter: Joe Stano
• Created: 02/Mar/10 11:30
• Updated: 15/Jul/10 13:41
• Resolved: 15/Jul/10 13:39

Description

My build project parses a project's pom.xml to expose the data to various ant tasks. After parsing the pom.xml, the ant tasks use the normal variable syntax such as ${project.build.directory} to dig into the pom's contents.

The value of this specific element in my project is "${basedir}/target". In 2.0.10, the resulting value of this lookup will be fully resolved to the project's directory. With 2.1.0, the value resolves to the literal "${basedir}/target" and the build fails.

2.1.0 failure with a ${project.build.directory} value of "${basedir}\target":

java.io.FileNotFoundException: c:\Projects\ProjectName\${basedir}\target\version.jsp (The system cannot find the path specified)

Issue Links

• duplicates: MANTTASKS-173 Value of project.build.finalName is not resolved
• is duplicated by: MANTTASKS-187 maven ant tasks 2.1.0 pom task no longer extrapolates properties
• relates to: MANTTASKS-183 Property not evaluated in pom/project/parent/version