On Wed, Dec 16, 2009 at 4:32 PM, Ian Dees <[email protected]> wrote: > Following this, it appears that any subsequent calls to that resource > immediately respond with a 404 without checking any proxy connections.
There are probably a couple of things going on here. The first is that by default, Maven itself will only check a repo for something once a day, even though the build output can make it look like it is trying to connect. While you're debugging this, you may need to clear your local repository (or at least the sub-tree of the offending artifact) to make sure the Maven client does not remember anything. You can also try using -U on the command line to force updates. On the Archiva side, check the configuration for the proxies. I believe there are settings for whether it should cache failures. -- Wendy
