[MNG-3057] properties not expanded in generated POMs when building A/B/C nested projects

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.7
• Fix Version/s: 2.1.0
• Component/s: Inheritance and Interpolation
• Assignee: John Dennis Casey
• Reporter: George Armhold
• Created: 15/Jun/07 09:58
• Updated: 06/Apr/15 00:00
• Resolved: 24/Feb/09 11:10

Description

Using Maven version: 2.0.8-SNAPSHOT, svn r547427.

I checked out and built 2.0.8 because I was interested in Jason van Zyl's patch for MNG-2619- "building from the middle pom of a (parent,child,grandchild) heirarchy fails". The fix works for the most part, but there still seems to be a problem with the poms that get generated during the install goal. The poms that get installed into .m2/repository do not have properties interpolated. If I run maven like:

$ mvn install -Dglobal-version=1.0.0

I get poms with the string "${global-version}" embedded in the resulting poms rather than what I specify on the command line (or in settings.xml). The build works properly aside from this, and if I do "mvn help:effective-pom" the properties are correctly interpolated.

I've attached a tarfile with an example A/B/C build structure that exhibits this behavior, as well as the generated poms.

Many thanks for your attention.

Issue Links

• is duplicated by: MDEPLOY-94 Variables in the version element in pom.xml need to be expanded before deployment
• is duplicated by: MINSTALL-50 provide property filtering on .pom files placed in local repo
• is related to: MNG-2619 building from the middle pom of a (parent,child,grandchild) heirarchy fails
• is related to: MNG-2820 Deployment is stripping out the license header from the POM
• is related to: MNG-3538 Properties inside <dependency> are not replaced in resulting POM
• is related to: MNG-3782 Variable substition not performed in transitive dependency using value from active profile
• is related to: MNG-4167 version-expression transformation interferes with plugins like GPG
• relates to: MNG-2971 Variables are not replaced into installed pom file
• relates to: MNG-4140 Properties incorrectly replaced in pom
• relates to: MNG-2412 global variable filtering of pom.xml for parent and sub module pom.xml files is not working when deploying to a repository.
• relates to: MNG-4223 Resolve expressions in POM artifact coordinates
• relates to: MNG-2446 parent Pom properties not resolved for module dependencies
• relates to: MNG-624 automatic parent versioning