[
https://issues.apache.org/jira/browse/MENFORCER-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17485214#comment-17485214
]
Delany commented on MENFORCER-396:
----------------------------------
I don't know what was going on here, but it works now.
The example code is still broken though.
One strange thing I did notice is that the allowedRepositories tag can have an
allowedPluginRepository tag.
> Faulty banned repositories
> --------------------------
>
> Key: MENFORCER-396
> URL: https://issues.apache.org/jira/browse/MENFORCER-396
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Components: Standard Rules
> Affects Versions: 3.0.0
> Reporter: Delany
> Priority: Minor
> Attachments: pom.xml
>
>
> To start with, the sample XML on
> [https://maven.apache.org/enforcer/enforcer-rules/bannedRepositories.html] is
> invalid.
> After correcting the XML, if I choose to whitelist, I get
> {quote}Failed to execute goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce
> (enforce-banned-repositories) on project dummy: Unable to parse configuration
> of mojo org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce for
> parameter allowedRepositories: Cannot create instance of interface
> org.apache.maven.enforcer.rule.api.EnforcerRule:
> org.apache.maven.enforcer.rule.api.EnforcerRule.<init>()
> {quote}
> Then I try unsuccessfully to blacklist [http://0.0.0.0/*] and others. The
> dependency:list-repositories goal on the other hand manages to find this
> repository.
> [^pom.xml]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
