A repository is blacklisted once Maven detects a connection failure. The
back listing rest for the current Maven run.
In order to prevent that, you must configure your proxy settings in your
Maven settings file.
Jeff
On Feb 1, 2008 9:28 PM, Allen, Daniel [EMAIL PROTECTED] wrote:
Hi.
I'm
.
Thanks!
~Dan Allen
-Original Message-
From: simon [mailto:[EMAIL PROTECTED]
Sent: Friday, February 01, 2008 4:03 PM
To: Maven Users List
Subject: Re: Repository Blacklist
It seems to me that there was a similar question very recently, and that
the answer was that maven *does* remember
It seems to me that there was a similar question very recently, and that
the answer was that maven *does* remember blacklists across runs.
Dan, you could try doing
mvn -U install
(-U causes plugins to be updated)
Otherwise, try looking in ~/.m2, which is where maven stores a lot of
other stuff
: Repository Blacklist
It seems to me that there was a similar question very recently, and that
the answer was that maven *does* remember blacklists across runs.
Dan, you could try doing
mvn -U install
(-U causes plugins to be updated)
Otherwise, try looking in ~/.m2, which is where maven
On Feb 1, 2008 2:03 PM, simon [EMAIL PROTECTED] wrote:
It seems to me that there was a similar question very recently, and that
the answer was that maven *does* remember blacklists across runs.
It doesn't remember the blacklist. It does remember individual plugin
download failures by virtue
