You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "George Gastaldi (Jira)" <ji...@apache.org> on 2022/06/23 14:26:00 UTC
[jira] [Updated] (MENFORCER-422) Support declaring external banned dependencies in an external file
[ https://issues.apache.org/jira/browse/MENFORCER-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
George Gastaldi updated MENFORCER-422:
--------------------------------------
Description: 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 (was: 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)
> Support declaring external banned dependencies in an external file
> ------------------------------------------------------------------
>
> Key: MENFORCER-422
> URL: https://issues.apache.org/jira/browse/MENFORCER-422
> Project: Maven Enforcer Plugin
> Issue Type: New Feature
> Reporter: George Gastaldi
> Priority: Major
>
> 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.7#820007)