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 2022/11/17 20:52:00 UTC

[jira] [Closed] (MENFORCER-422) Support declaring external banned dependencies in an external file/URL

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

Slawomir Jaranowski closed MENFORCER-422.
-----------------------------------------
    Fix Version/s: next-release
         Assignee: Peter Palaga
       Resolution: Fixed

> Support declaring external banned dependencies in an external file/URL
> ----------------------------------------------------------------------
>
>                 Key: MENFORCER-422
>                 URL: https://issues.apache.org/jira/browse/MENFORCER-422
>             Project: Maven Enforcer Plugin
>          Issue Type: New Feature
>            Reporter: George Gastaldi
>            Assignee: Peter Palaga
>            Priority: Major
>             Fix For: next-release
>
>
> There are some use cases where the list of banned dependencies declared in an enforcer plugin configuration needs to be reused in another project. It would be nice if the {{bannedDependencies}} rule could read the list of banned dependencies from an external file/URL



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