[
https://issues.apache.org/jira/browse/MENFORCER-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17635843#comment-17635843
]
Jimisola Laursen commented on MENFORCER-422:
--------------------------------------------
[~gastaldi] It's not clear to me where I place files if I use "classpath:".
This is the classpath for Maven Enforcer and if so where is it per default and
can I change it? Or is it the classpath of the actual Maven project?
Will probably go with non-classpath option for now but it might need some
documentation. I looked at the PR and didn't see it explained there.
> 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)
