Ack, sorry to spam, but hit send too soon:
2009-12-15 17:04:33,179 [btpool0-13] ERROR
org.apache.maven.archiva.webdav.ArchivaDavResourceFactory - Failures occurred
downloading from some remote repositories:
central: Download failure on resource
[http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.4.1/maven-resources-plugin-2.4.1.jar]:Access
denied to:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.4.1/maven-resources-plugin-2.4.1.jar
org.apache.maven.archiva.policies.ProxyDownloadException: Failures occurred
downloading from some remote repositories:
central: Download failure on resource
[http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.4.1/maven-resources-plugin-2.4.1.jar]:Access
denied to:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.4.1/maven-resources-plugin-2.4.1.jar
Following this, it appears that any subsequent calls to that resource
immediately respond with a 404 without checking any proxy connections.
On Wed, 2009-12-16 at 17:27 -0600, Ian Dees wrote:
> Ok, I believe there is still an issue with this. Some more specifics:
>
> I'm running maven via the m2eclipse plugin, have an Archiva server at
> http://url:8080/archiva mirroring central, and also have the following
> in my ~/.m2/settings.xml:
>
> ...
> <mirror>
> <id>archiva.central</id>
> <url>http://url:8080/archiva/repository/internal</url>
> <mirrorOf>central</mirrorOf>
> </mirror>
> ...
>
> When I attempt to run the "install" maven goal, it can not resolve the
> maven-resources-plugin:2.4.1 (which clearly exists on repo1).
>
> archiva.log shows me:
>
>
> On Wed, 2009-12-16 at 16:14 -0600, Ian Dees wrote:
> > The corporate overlords here recently started blocking the official
> > Maven repo, so Archiva was getting 403 Forbidden when it tried to hit
> > the repo. I changed the proxy to one that works now, but Archiva refuses
> > to forget that it has got a 403 last time it touched central.
> >
> > How can I get it to hit the repo and realize that it is OK to use the
> > new proxy now?
>
