On 01/08/2007, at 4:01 PM, Milos Kleint wrote:
AFAIK that's intentional. To avoid people downloading the whole
repo through wget. rsynch is the preferred method I think.
Then why is curl not rejected? Why is Archiva failing? Why is my
local mvn retrieval also failing?
I'm happy to
Others have reported similar problems with wget. Without knowing this
for certain, I would assume that the repo1 owners simply do not like
people using wget to pull their entire repo down, so they might be
blocking it somehow. I believe the Maven website instructs people to
use rsync if they want
It looks like your running a *nix, but can you tell us specifically
what OS, JDK version, Maven version, etc? We've had Windows users run
into similar problems who were having troubles due to overzealous
antivirus software, etc.
maven 2.0.6 running on both OSX and RedHat EL3 (happens across
AFAIK that's intentional. To avoid people downloading the whole repo
through wget. rsynch is the preferred method I think.
Milos
Paul Smith wrote:
This has happened before, and then appeared to magically resolve
itself, but it's quite sticky at the moment.
It seems to stem from this
This has happened before, and then appeared to magically resolve
itself, but it's quite sticky at the moment.
It seems to stem from this weirdness. Given a URL on the central Repo:
http://repo1.maven.org/maven2/org/apache/maven/maven/2.0.6/
maven-2.0.6.pom
1) I can browse using Firefox -
