You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Simon Wang (JIRA)" <ji...@codehaus.org> on 2014/05/28 12:07:10 UTC

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

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

Simon Wang updated MENFORCER-193:
---------------------------------

          Component/s: Standard Rules
          Description: 
*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.
    Affects Version/s: 2.0
        Fix Version/s: 2.0
              Summary: Add new rule: BannedRepositories to ban specified repositories for whole maven session  (was: Add new rule)

> 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
>             Fix For: 2.0
>
>
> *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)