You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Elliotte Rusty Harold (Jira)" <ji...@apache.org> on 2020/07/29 10:12:00 UTC
[jira] [Resolved] (MENFORCER-256) BannedDependencies does not work
with wildcard strings
[ https://issues.apache.org/jira/browse/MENFORCER-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Elliotte Rusty Harold resolved MENFORCER-256.
---------------------------------------------
Resolution: Fixed
> BannedDependencies does not work with wildcard strings
> ------------------------------------------------------
>
> Key: MENFORCER-256
> URL: https://issues.apache.org/jira/browse/MENFORCER-256
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Affects Versions: 1.4
> Reporter: Dariusz Kordonski
> Priority: Major
>
> Wildcards mixed with strings don't seem to work with BannedDependencies, despite being documented as a valid exclusion pattern here: http://maven.apache.org/enforcer/enforcer-rules/bannedDependencies.html.
> Pure wildcards (for the entire component) seem to work, though. E.g. both excludes below will work (exact match, pure wildcard):
> {code}
> <excludes>
> <exclude>com.atlassian.plugins:atlassian-plugins-core</exclude>
> </excludes>
> {code}
> {code}
> <excludes>
> <exclude>com.atlassian.plugins:*</exclude>
> </excludes>
> {code}
> But the following will not be detected (mixed string and wildcards), despite being documented as a valid exclusion pattern:
> {code}
> <excludes>
> <exclude>com.atlassian.plugins:atlassian-plugins-*</exclude>
> </excludes>
> {code}
> We are using version 1.4.0
--
This message was sent by Atlassian Jira
(v8.3.4#803005)