Tamas Cservenak opened MNG-8256 and commented
The FilteredProjectDependencyGraph is used to "narrow" reactor when constrained projects are used (ie use of -pl and alike of methods). The code was correct when transitive upstream or downstream in-project dependencies were asked, but in case of non-transitive ones the links were lost, if "intermediary" was removed from reactor.
In case of modules (A, B, C) and relationship A -> B -> C if active projects were only (A, C), the filtered links should result in (A -> C), unlike today, in A and C being "unrelated" that is simply no true.
Issue Links:
- MNG-8096 Inconsistent dependency resolution behaviour for concurrent multi-module build can cause failures
("fixes")
Remote Links:
Backported to: 4.0.0-beta-5, 3.9.10