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 like cached passwords. Regards, Simon On Fri, 2008-02-01 at 21:52 +0100, Jeff MAURY wrote: > 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 using Maven2, and without telling me, the company I'm at recently > > put up a proxy between the office and the web. So, when I tried to use > > Maven with a new plugin, it attempted to get that from the central > > repository, failed because I hadn't set up the proxy settings, and then > > blacklisted the central repository. > > > > Can anyone tell me where the settings for that blacklist are so that I > > can remove the strike against Central? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
