[
https://issues.apache.org/jira/browse/MNG-8256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak reassigned MNG-8256:
------------------------------------
Assignee: Tamas Cservenak
> ProjectDependencyGraph bug: in case of filtering, non-direct module links are
> lost
> ----------------------------------------------------------------------------------
>
> Key: MNG-8256
> URL: https://issues.apache.org/jira/browse/MNG-8256
> Project: Maven
> Issue Type: Bug
> Components: Core
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 4.0.0, 3.9.10, 4.0.0-beta-5
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
