Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.0.2
-
Component/s: Inheritance and Interpolation
-
Labels:None
-
Complexity:Intermediate
-
Number of attachments :
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
| This issue relates to: | ||||
| MNG-3355 | CLONE -${pom.build.sourceDirectory} and ${pom.build.testSourceDirectory} no longer recognized |
|
|
|
| MNG-3475 | Some directories are not basedir aligned |
|
|
|
| This issue is related to: | ||||
| MNG-2186 | POM interpolation problem in maven-2.0.3 |
|
|
|
| MNG-3530 | Regression: Properties get resolved before the LifeCycle is Forked. |
|
|
|
its been noted that this isn't always the case, depending on environment. This leads me to believe it could be related to the introduction of environment variables in the expression evaluator.