Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.2.1, 3.0.3
-
None
Description
Running mvn clean package site on the attached multi-module test project fails with a dependency resolution issue. While the main build still builds the aggregator module, an aggregator (report) mojo forks the lifecycle and despite this forked lifecycle executing up to "package" phase, reactor resolution inside this forked lifecycle fails since the wrong project instances (those from the main build instead of the forked build) are searched for build output.