Maven 2 & 3

Incorrect resolution of parent POM properties

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Blocker Blocker
  • Resolution: Fixed
  • Affects Version/s: 2.0.2
  • Fix Version/s: 2.0.3
  • Component/s: Inheritance and Interpolation
  • Labels:
    None
  • Environment:
    Windows XP, JDK 1.4.2_11
  • Complexity:
    Intermediate
  • Number of attachments :
    1

Description

Unzip maven-bug to current dir and cd to maven-bug/artifact.

Now, Maven 2.0.1 handles things correctly (irrelevant output removed):

[echo] Parent: parentartifact, project: artifact

But Maven 2.0.2 has a bug:

[echo] Parent: artifact, project: artifact

Issue Links

This issue relates to:
MNG-3530 Regression: Properties get resolved before the LifeCycle is Forked. Major Closed
MNG-3355 CLONE -${pom.build.sourceDirectory} and ${pom.build.testSourceDirectory} no longer recognized Major Closed
This issue is related to:
MNG-2186 POM interpolation problem in maven-2.0.3 Critical Closed

Activity

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

promoting if it is a regression

Show
Brett Porter added a comment - promoting if it is a regression
Hide
Permalink
Mauro Talevi added a comment -

Don't know if related to this bug, but there seems to be another regression issue with 2.0.3-SNAPSHOT:

If the parent pom (SNAPSHOT version) is not found in remote repo mvn chokes and does not generate it as it should when running from top-level.

This behaviour does not appear in 2.0.2 so is definitely a regression.

Show
Mauro Talevi added a comment - Don't know if related to this bug, but there seems to be another regression issue with 2.0.3-SNAPSHOT: If the parent pom (SNAPSHOT version) is not found in remote repo mvn chokes and does not generate it as it should when running from top-level. This behaviour does not appear in 2.0.2 so is definitely a regression.
Hide
Permalink
Mauro Talevi added a comment -

Created MNG-2130 to track the inability to re-created parent POM - as seems sufficient different in scope.

Show
Mauro Talevi added a comment - Created MNG-2130 to track the inability to re-created parent POM - as seems sufficient different in scope.
Hide
Permalink
John Casey added a comment -

this seems to have to do with trimming the root token from an expression before evaluating it, even though that's already been done...

Show
John Casey added a comment - this seems to have to do with trimming the root token from an expression before evaluating it, even though that's already been done...
Hide
Permalink
John Casey added a comment -

see it0088 and it0100 (it0100 has the test case provided in this report, slightly modified to fit the integration testing framework).

Show
John Casey added a comment - see it0088 and it0100 (it0100 has the test case provided in this report, slightly modified to fit the integration testing framework).
Hide
Permalink
Kjetil Ødegaard added a comment -

Great! Looks like this fixed my problem.

Show
Kjetil Ødegaard added a comment - Great! Looks like this fixed my problem.

People

Vote (1)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.