GitHub user wangyf2010 opened a pull request:
https://github.com/apache/maven-enforcer/pull/13
[MENFORCER-193]: Add new rule: BannedRepositories to ban specified repos...
There are use cases that need to ban specified repositories.
Ex. one enterprise migrate their repositories from old one to new one.
But some users still use old settings.xml or some projects' pom.xml still
have old repositories.
What this rule did:
1. bannedRepositories: user could add banned repositories and support
wildcard "*" to simplify user's usage.
2. allowedRepositories: that's simpler and useful for enterprise users.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/wangyf2010/maven-enforcer trunk
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/maven-enforcer/pull/13.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #13
----
commit e5d5dc91a51ca552b9da2f2dada0825fe04ffdc6
Author: Simon, Wang <yunfw...@ebay.com>
Date: 2014-05-28T10:06:33Z
[MENFORCER-193]: Add new rule: BannedRepositories to ban specified
repositories for whole maven session
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
