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/19 14:31:00 UTC

[jira] [Assigned] (MENFORCER-276) Allow ignoring dependency scopes in RequireUpperBoundDeps

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

Slawomir Jaranowski reassigned MENFORCER-276:
---------------------------------------------

    Assignee: Slawomir Jaranowski

> Allow ignoring dependency scopes in RequireUpperBoundDeps
> ---------------------------------------------------------
>
>                 Key: MENFORCER-276
>                 URL: https://issues.apache.org/jira/browse/MENFORCER-276
>             Project: Maven Enforcer Plugin
>          Issue Type: New Feature
>          Components: requireUpperBoundDeps, Standard Rules
>            Reporter: Oleg Nenashev
>            Assignee: Slawomir Jaranowski
>            Priority: Major
>             Fix For: 3.3.0
>
>
> We have recently adopted RequireUpperBoundDeps in the Jenkins project (https://github.com/jenkinsci/plugin-pom/pull/67). In order to implement it, [~jglick@netbeans.org] added a support of ignoring particular dependencies in MENFORCER-273.
> Sometimes we declare dependencies between plugins for testing purposes (scope=test), and in such case RequireUpperBoundDeps fails the build if there is a test dependency conflicting with the main code. Although it may cause instability of tests (including false positive results), it does not really impact the distributable package in our case.
> I propose to add another option for filtering of dependency scopes.



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