[
https://issues.apache.org/jira/browse/MENFORCER-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17635870#comment-17635870
]
George Gastaldi commented on MENFORCER-422:
-------------------------------------------
That's the plugin's classpath. The idea is that you bundle the enforcer rules
in a maven artifact and add a \{{<dependency>}} to that artifact in the
maven-enforcer-plugin dependencies' element
> 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)
