[MNG-1927] ${project.build.directory} different in M2.0 & M2.0.1

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 2.0.2
• Component/s: Inheritance and Interpolation
• Assignee: Jason van Zyl
• Reporter: Brett Porter
• Created: 05/Jan/06 18:02
• Updated: 07/Apr/15 12:24
• Resolved: 13/Jan/06 23:09

Description

From Jens:
In Maven 2.0 the value containes the whole absolute path to the target
dir.

C:\windows\system32\target

With Maven 2.0.1 only:

target\

(Note: I was unable to reproduce this against 2.0, instead getting ${project.build.directory} verbatim, but I believe it should be an absolute path)

Issue Links

• is related to: MNG-2186 POM interpolation problem in maven-2.0.3
• is related to: MNG-3530 Regression: Properties get resolved before the LifeCycle is Forked.
• relates to: MNG-3355 CLONE -${pom.build.sourceDirectory} and ${pom.build.testSourceDirectory} no longer recognized
• relates to: MNG-3475 Some directories are not basedir aligned