[
https://issues.apache.org/jira/browse/MENFORCER-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17331106#comment-17331106
]
Matt Nelson commented on MENFORCER-376:
---------------------------------------
Is there a way to signal this issue should be a blocker for the next release
3.0.0 or 3.0.0-M4? The changes proposed here are non passive to the yet to be
released changes from MENFORCER-338. I want to protect against a scenario where
enforcer is released without this change, thus preventing it from being
accepted due to being non passive.
> Add support for excludes/includes in requireJavaVendor rule
> -----------------------------------------------------------
>
> Key: MENFORCER-376
> URL: https://issues.apache.org/jira/browse/MENFORCER-376
> Project: Maven Enforcer Plugin
> Issue Type: Improvement
> Components: Standard Rules
> Affects Versions: 3.0.0-M3
> Reporter: Krosheninnikov Artem
> Priority: Major
>
> There was a suggestion here [1] to add includes/excludes support in
> requireJavaVendor rule. Right now it's not clear how it would work if you
> define the same vendor name in exclude and include lists but implementation
> can be more or less copied from BannedDependencies rule.
> [1]
> https://issues.apache.org/jira/browse/MENFORCER-338?focusedCommentId=17169044&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17169044
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
