[MNG-8256] ProjectDependencyGraph bug: in case of filtering, non-direct module links are lost

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.9.10, 4.0.0-beta-5, 4.0.0
• Component/s: Core
• Assignee: Tamas Cservenak
• Reporter: Tamas Cservenak
• Created: 12/Sep/24 16:05
• Updated: 12/Sep/24 20:51
• Resolved: 12/Sep/24 20:51

Description

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

• fixes: MNG-8096 Inconsistent dependency resolution behaviour for concurrent multi-module build can cause failures
• links to: GH PR #1723
• links to: GitHub Pull Request #1723
• links to: GitHub Pull Request #1724