[MNG-3535] Valid properties which look self referential fail to resolve

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.9
• Fix Version/s: 2.1.0-M1
• Component/s: Inheritance and Interpolation
• Assignee: John Dennis Casey
• Reporter: Chris Custine
• Created: 19/Apr/08 18:34
• Updated: 05/Sep/15 22:06
• Resolved: 25/Jun/08 15:55

Description

In 2.0.9 properties which look self referential but would otherwise resolve to a system property are failing due to fixes for MNG-2339. Current example is any version of jruby shared pom at
http://repo1.maven.org/maven2/org/jruby/shared/1.0.1/shared-1.0.1.pom

which contains:

<java.specification.version>${java.specification.version}</java.specification.version>

The question is whether this should be valid or not, but it has worked in every version up to and including 2.0.8 because System properties were available in the first interpolate step. In 2.0.9 this first pass does not include the system props and an exception is thrown because of the self reference check.

Issue Links

• is related to: MNG-3536 REGRESSION: pom.build.sourceDirectory in Maven 2.0.9: it doesn't work anymore
• is related to: MNG-3070 ${x} properties no longer expanded in </version> tag after 2.0.3
• relates to: MNG-3746 POM properties do not override default system properties during POM interpolation
• relates to: MNG-2562 expose current time as a property for POM interpolation