[MNG-5890] In reactor projects, having a "root" counterpart to "project" properties would be useful

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Won't Do
• Affects Version/s: 3.3.3
• Component/s: Bootstrap & Build, Core, General
• Assignee: Unassigned
• Reporter: Jordan Zimmerman
• Created: 16/Sep/15 15:40
• Updated: 20/Dec/19 14:54
• Resolved: 20/Dec/19 14:54

Description

Often, in reactor builds, modules need to refer to properties relative to the root pom. E.g.:

root-pom.xml
\___ module1-pom.xml
         \___ sub-module1-pom.xml
\___ module2-pom.xml
         \___ sub-module2-pom.xml

In this example, there's no way to set a dependency in the root pom that uses the root pom's parent version. This is because ${project.parent.version} will be evaluated relatively in module1/2 and sub-module1/2. In module1/2, it will refer to the root's parent. But, in sub-module1/2 it will refer only to the root.

Ideally, we could do something like this:

<parent>
    <groupId>my.group</groupId>
    <artifactId>foo</artifactId>
    <version>1.2.3</version>
</parent>

<dependencyManagement>
    <dependencies>
        <dependency>
            <groupId>my.group</groupId>
            <artifactId>a-different-artifact-in-my.group</artifactId>
            <version>${root.parent.version}</version>
        </dependency>
    </dependencies>
</dependencyManagement>

With this "root" feature, ${root.parent.version} would refer to the same value at every level of the reactor build.

Issue Links

• is related to: MNG-5900 early interpolation: support ${this.*} as expression
• relates to: MPH-106 add gav parameter to calculate effective pom for any gav, not only reactor