You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Slawomir Jaranowski (Jira)" <ji...@apache.org> on 2023/03/23 21:16:00 UTC

[jira] [Closed] (MENFORCER-474) Filtering dependency tree by scope

     [ https://issues.apache.org/jira/browse/MENFORCER-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Slawomir Jaranowski closed MENFORCER-474.
-----------------------------------------
    Resolution: Fixed

> Filtering dependency tree by scope
> ----------------------------------
>
>                 Key: MENFORCER-474
>                 URL: https://issues.apache.org/jira/browse/MENFORCER-474
>             Project: Maven Enforcer Plugin
>          Issue Type: Bug
>          Components: Standard Rules
>            Reporter: Slawomir Jaranowski
>            Assignee: Slawomir Jaranowski
>            Priority: Major
>             Fix For: 3.3.0
>
>
> In current implementation we change default {{dependencySelector}}
>  for {{repositorySystemSession}}
> It has an impacts for whole dependency tree resolving.
> We should filter dependencies scopes on project level, for transitive dependency tree we should not change defaults selectors.
>  
> It is cause of issues as: 
>  - MENFORCER-467 - no scope filtering - everything is resolved in every scope
>  - MENFORCER-466
>  - MENFORCER-470 - when we allow changing scope we will have impacts on whole tree



--
This message was sent by Atlassian Jira
(v8.20.10#820010)