Maven 2 & 3

${project.build.directory} different in M2.0 & M2.0.1

Details

  • Complexity:
    Intermediate
  • Number of attachments :
    0

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

Bug - A problem which impairs or prevents the functions of the product. MNG-2186 POM interpolation problem in maven-2.0.3

  • Critical - Crashes, loss of data, severe memory leak.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Bug - A problem which impairs or prevents the functions of the product. MNG-3530 Regression: Properties get resolved before the LifeCycle is Forked.

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
relates to

Bug - A problem which impairs or prevents the functions of the product. MNG-3355 CLONE -${pom.build.sourceDirectory} and ${pom.build.testSourceDirectory} no longer recognized

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Bug - A problem which impairs or prevents the functions of the product. MNG-3475 Some directories are not basedir aligned

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Brett Porter added a comment -

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.

Show
Brett Porter added a comment - 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.
Hide
Permalink
Jason van Zyl added a comment -

Interpolator from 2.0 back ported with envar interpolation taken from the new interpolator to keep compatibility with that feature which was added in 2.0.1.

Show
Jason van Zyl added a comment - Interpolator from 2.0 back ported with envar interpolation taken from the new interpolator to keep compatibility with that feature which was added in 2.0.1.

People

  • Assignee:
    Jason van Zyl
    Reporter:
    Brett Porter
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: