[MPH-85] effective-pom should resolve properties in submodules

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 2.1.1
• Component/s: effective-pom

Environment

mvn --version
Apache Maven 3.0.4-RC3 (r1210461; 2011-12-05 14:58:54+0100)
Maven home: /usr/local/Cellar/maven/current/libexec
Java version: 1.6.0_29, vendor: Apple Inc.
Java home: /Library/Java/JavaVirtualMachines/1.6.0_29-b11-402.jdk/Contents/Home
Default locale: de_DE, platform encoding: MacRoman
OS name: "mac os x", version: "10.7.2", arch: "x86_64", family: "mac"

• Assignee: Guillaume Boué
• Reporter: Mirko Friedenhagen
• Created: 07/Dec/11 14:36
• Updated: 12/Nov/16 18:38
• Resolved: 12/Nov/16 18:38

Description

When defining the scm in the parent and referencing it in the
module projects I would expect help:effective-pom to resolve these.

Right now running {{

{mvn clean install site site:stage}

}} is resolving
this IMO correctly as specified in source-repository.html
while in the the output of help:effective-pom leaves the properties alone.

I have assembled a small multi-module project to show the effect.

Run

mvn clean install site site:stage
mvn help:effective-pom -Doutput=target/ep.xml

The original code may be seen at https://github.com/mfriedenhagen/multi-module-sample/tree/help-effective-pom

This is maybe somewhat related to MPIR-234.

Issue Links

• is related to: MNG-5784 SO question regarding replacing name tag with ${project.parent.name} does not work in multi module builds.