[
https://issues.apache.org/jira/browse/MENFORCER-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17929449#comment-17929449
]
Jacques Burns commented on MENFORCER-519:
-----------------------------------------
Right. In most cases, it really only matters that the dependency does not
appear in the release artifact, or as a dependency to it. For this specific use
case, though, my thinking was that a little bit of duplication was not the end
of the world.
If that's not the case, though, would you prefer to see it as a configuration
option to the `BannedDependencies` rule?
> "BannedPluginDependencies" Rule
> -------------------------------
>
> Key: MENFORCER-519
> URL: https://issues.apache.org/jira/browse/MENFORCER-519
> Project: Maven Enforcer Plugin
> Issue Type: Wish
> Components: Standard Rules
> Reporter: Jacques Burns
> Priority: Minor
>
> We ran into this issue at work where we had to prevent a certain JAR from
> ever appearing in the local repository of our build server. I was thinking of
> solving this with the Enforcer plugin, but it turns out that the JAR is also
> a dependency of some of the Maven plugins we use, and the Enforcer plugin
> doesn't check that. I realise it could probably be a custom rule, but maybe
> there could be a general desire for that kind of functionality.
> I'm willing to do the work on this and submit the PR, but first, is it
> something you folks would like added?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
