Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm currently attempting to set up a proxy repository (as described in the Nexus guide) for the Bukkit repository, in order to build some dependent projects locally. I'm using the URL:

It seems to be the right URL, but no matter my configuration, I can't seem to get Nexus to actually proxy any artifacts through the repository. I've tried:

  • Using different IDs in the local Nexus version, both bukkit (my desired ID) and bukkit_repos (to match the remote repo)
  • Changing the policy of the repo from Release to Snapshot, and even recreating the repo with the different policies
  • Adding the URL above as a mirror
  • Expiring the cache, rebuilding the index, and updating the index

No matter what I try, I can't get any artifacts to appear in the proxy. What am I missing?

share|improve this question
Does that URL work as a repository in your settings.xml? That'd be the first thing that I check to make sure it's "maven-friendly". – Ken Dec 9 '11 at 6:50
The build works when I place that URL in my settings.xml as a repository. What's more, after I woke up this morning, Nexus had proxied this repository; however, I can still produce this problem with new proxy repos. Is there just a several-hour lag involved in the proxy operation? – Tim Dec 9 '11 at 15:10

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.