Maven 4.0.0-rc-4 fails dependency resolution if distributionManagement is defined in parent

[dmitry-lt]

Affected version

4.0.0-rc-4

Bug description

Using the Maven 4.0.0-rc-4 wrapper, create a project with a pom.xml containing:

<parent>
    <groupId>org.apache</groupId>
    <artifactId>apache</artifactId>
    <version>35</version>
</parent>

and

<dependencies>
    <dependency>
        <groupId>org.apache.hadoop</groupId>
        <artifactId>hadoop-client</artifactId>
        <version>3.4.1</version>
    </dependency>
</dependencies>

Run ./mvnw validate

Expected
The project validates successfully (as it does when using Maven 3.9.11 or 4.0.0-rc-3).

Actual
The validation fails with:
Could not collect dependencies for project org.example:untitled17:jar:1.0-SNAPSHOT
[ERROR] java.lang.IllegalArgumentException: Invalid Version Range Request: org.apache:apache:pom:21 < [central (https://repo.maven.apache.org/maven2, default, releases), apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots, default, releases+snapshots), repository.jboss.org (https://repository.jboss.org/nexus/content/groups/public/, default, releases), ${distMgmtSnapshotsId} (${distMgmtSnapshotsUrl}, default, releases+snapshots)]

Reproducer
Reproducer project attached: untitled17.zip

[cstamas]

If you do mvn -e you will see the cause. Sadly, it is buried under layers of abstraction, and is most probably something along lines of java.lang.IllegalArgumentException: Not fully interpolated remote repository ... or similar...

Reproducer does:

Suppressed: java.lang.IllegalArgumentException: Not fully interpolated remote repository ${distMgmtSnapshotsId} (${distMgmtSnapshotsUrl}, default, releases+snapshots)

Maven 3 was "permissive" with these clearly broken setups (some POM defines a remote repository that is not known at the build time as URL property is unknown). Maven4 refuses to build projects like these as they cannot be reproducible

Nope, this is real bug here, parent own properties are not considered when own repositories are to be interpolated. Also, this is not about distMgmt at all, is unused during consuming them. The parent defined one is interpolated okay.

The problem occurs when hadoop-thirdparty parent is processed (as part of getting all the models) and it also defines a remote repository with same properties.

[cstamas]

PR is #11037 makes this reproducer not reproduce anymore.