Number of attachments :
We've defined three repositories in my current, maven-based project. Our team has it's own repository, we have a company-wide repository and there is, of course, the iblio repository.
The team and company-wide repository are used to get and store internal artifacts which have no meaning for the rest of the world. Whatever we need from the outer world is usually part of the iblio repository.
Having evaluated maven-proxy as a central repository for our team I noticed that whenever our build (i.e maven) asks the maven-proxy to server snapshots of team- or company-specific jars these requests are also forwarded to the ibiblio repo. We consider this is a problem as
a) we do not want to let whoever know that we're currently working on top-secret-product-SNAPSHOT.jar and
b) iblio access is - from time to time - quite slow.
A possible solution for this could be to add a configuration option in maven-proxy. Something like: Ask repo.1 for artifacts with groupId "this" (should be a regexp or ant style include pattern). A kind of filter, includes and excludes, defining which repos are asked for what artefacts.