[jira] (MENFORCER-193) Add new rule: BannedRepositories to ban specified repositories for whole maven session

["Karl-Heinz Marbaise (JIRA)" <ji...@codehaus.org>]

     [ https://jira.codehaus.org/browse/MENFORCER-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl-Heinz Marbaise closed MENFORCER-193.
-----------------------------------------

    Resolution: Fixed
      Assignee: Karl-Heinz Marbaise

Fixed in [r1602751|http://svn.apache.org/r1602751].
Thanks for the contribution Simon.

> Add new rule: BannedRepositories to ban specified repositories for whole maven session
> --------------------------------------------------------------------------------------
>
>                 Key: MENFORCER-193
>                 URL: https://jira.codehaus.org/browse/MENFORCER-193
>             Project: Maven Enforcer Plugin
>          Issue Type: New Feature
>          Components: Standard Rules
>    Affects Versions: 2.0
>            Reporter: Simon Wang
>            Assignee: Karl-Heinz Marbaise
>             Fix For: 1.4
>
>
> *Description*
> 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.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)