[MNG-6160] Forking process not always aware of reactor projects

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.3.9
• Fix Version/s: 4.0.0-alpha-2, 4.0.0
• Component/s: Reactor and Workspace
• Assignee: Maarten Mulders
• Reporter: Robert Scholte
• Created: 22/Jan/17 19:39
• Updated: 20/Oct/22 08:11
• Resolved: 17/Jul/20 06:17

Description

While running mvn clean -e -Preporting site on the Maven Artifact Resolver 1.0.3-SNAPSHOT I noticed downloads of files which should be part of the reactor.

[INFO] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
[INFO] Forking Maven Artifact Resolver SPI 1.0.3-SNAPSHOT
[INFO] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Downloading: https://repository.apache.org/snapshots/org/apache/maven/resolver/maven-resolver-api/1.0.3-SNAPSHOT/maven-resolver-api-1.0.3-20170122.151134-3.pom
Downloaded: https://repository.apache.org/snapshots/org/apache/maven/resolver/maven-resolver-api/1.0.3-SNAPSHOT/maven-resolver-api-1.0.3-20170122.151134-3.pom (2 KB at 1.6 KB/sec)

There are 2 issues with this:

• Maven is using other files than the expectd files from the reactor
• In case those files don't exist it'll fail.

See log file for complete evidence

Issue Links

• depends upon: MNG-4660 Use of --resume-from in multi-module project fails with missing inter-module dependencies