[MASSEMBLY-189] plugin not correctly interpolating POM variables like project.build.directory

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.1
• Fix Version/s: 2.2-beta-2
• Environment: I used both released version 2.1 and also 2.2-SNAPSHOT
• Assignee: John Dennis Casey
• Reporter: raysuliteanu
• Created: 08/Mar/07 14:11
• Updated: 14/Feb/08 15:36
• Resolved: 14/Feb/08 15:36

Description

I have a assembly descriptor file with ${project.build.directory} in the <source> element of a <file>. I get an error "Failed to create assembly: File to filter not found" because the file path has "${project.build.directory}" rather than the value of ${project.build.directory}.

I have traced the problem to AssemblyInterpolator.interpolateElementValue(). It tries to look up build.directory in ReflectionValueExtractor.evaluate() rather than project.build.directory, and it can't evaluate build.directory. A hack workaround is ...

if (value == null)
{
try
{
value = ReflectionValueExtractor.evaluate(realExpr, project);
if (value == null)
{
// HACK: strip ${ and } and retry
wholeExpr = wholeExpr.substring(2, wholeExpr.length() - 1);
value = ReflectionValueExtractor.evaluate(wholeExpr, project);
}
}

Issue Links

• is duplicated by: MASSEMBLY-266 Property expansion does not work for ${project.build.finalName} in descriptor file