You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Stephen Connolly (JIRA)" <ji...@codehaus.org> on 2009/11/21 12:56:55 UTC
[jira] Closed: (MENFORCER-86) Add a banRepositories rule
[ http://jira.codehaus.org/browse/MENFORCER-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephen Connolly closed MENFORCER-86.
-------------------------------------
Resolution: Duplicate
Fix Version/s: 1.0-beta-1
Aha! The project site does not give details, but this feature is already available as of 1.0-beta-1
<requireNoRepositories>
Sorted
> Add a banRepositories rule
> --------------------------
>
> Key: MENFORCER-86
> URL: http://jira.codehaus.org/browse/MENFORCER-86
> Project: Maven 2.x Enforcer Plugin
> Issue Type: New Feature
> Components: Standard Rules
> Reporter: Stephen Connolly
> Fix For: 1.0-beta-1
>
>
> This rule is needed so that we can enforce the "no repositories" requirement of Maven Central Repository.
> I would see something like (these would be defaults>
> <banRepositories>
> <allowSnapshots>true</allowSnapshots> <!-- if a repo can resolve -SNAPSHOTs, I'm ok with it being in the pom -->
> <allowReleases>false</allowReleases> <!-- if a repo can resolve releases, these two defaults would result in -SNAPSHOT only repositories being allowed by default -->
> <ignoreRepositories>
> <!--ignoreRepository>id of repository</ignoreRepository-->
> </ignoreRepositories>
> </banRepositories>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira