You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2022/06/23 18:56:00 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17558194#comment-17558194 ] 

Michael Osipov commented on MENFORCER-422:
------------------------------------------

Ideally as plugin dependencies on the plugin's classpath. Similar to remote resources.

> 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
>            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)