[MNG-6090] CI friendly properties break submodule builds

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.3.9
• Fix Version/s: 3.5.0-beta-1, 3.5.0
• Component/s: Core
• Assignee: Karl Heinz Marbaise
• Reporter: Harald Wellmann
• Created: 14/Sep/16 16:08
• Updated: 28/Mar/20 15:01
• Resolved: 13/Mar/17 21:53

Description

Scenario

A multi-module project where the parent version is one of the CI friendly properties, e.g. ${revision} as outlined in http://blog.soebes.de/blog/2016/08/08/maven-how-to-create-a-release/.

There are two submodules submodule1 and submodule2 such that submodule2 depends on submodule1.

Expected behaviour

Each submodule can be built by itself, e.g.

mvn clean install -Drevision=1.0.0-SNAPSHOT -pl submodule2

or

cd submodule2; mvn clean install -Drevision=1.0.0-SNAPSHOT

Actual behaviour

This does not work for submodule2 or in general any module that depends on a module from the same reactor.

Maven cannot resolve the property variable in the referenced parent POM version and fails the build:

[ERROR] Failed to execute goal on project submodule2: Could not resolve dependencies for project com.example:submodule2:jar:1.0.0-SNAPSHOT: Failed to collect dependencies at com.example:submodule1:jar:1.0.0-SNAPSHOT: Failed to read artifact descriptor for com.example:submodule1:jar:1.0.0-SNAPSHOT: Could not find artifact com.exammple:parent:pom:${revision} -> [Help 1]

There is no problem building submodule1 or the entire reactor.

Same problem observed with a local build from master (3.4.0-SNAPSHOT).

Issue Links

• is blocked by: MNG-6057 Problem with CI friendly usage of ${..} reactor order is changed
• is blocked by: MNG-5895 Problem with CI friendly usage of ${..} which is already defined via property in pom file.