Hej Guillaume!
gnodet wrote: > > When I did the release, I did ensure that all dependencies are available > from the listed repositories by trashing my m2 local repo. > Strange that it worked for you but not for me...I had those errors for two days, so it was not just a temporary thing of a couple of minutes. gnodet wrote: > > I'm trying to rebuild it to see if it still works. > It seems to work from me. Could you try with a clean repo ? > I just tried, now automatic downloading works fine :) gnodet wrote: > > You should not have to download manually any file, but retry until maven > downloads all the dependencies. > Well, 2-3 tries with always the same files being broken indicates it's not just a coincidence solving itself during the next minutes. As I wrote, a whole directory was not existing on all tried mirrors -- this will only be fixes when the mirrors are updated some hours later. My main point is not to get stuff done here for me (it took time but finally I had a running build). My point is how to avoid such problems in general. Obviously, my proposed solution 1 is not enough :-/ Georg -- View this message in context: http://www.nabble.com/Maven-using-limited-set-of-download-mirrors-%3D%3E-errors-tf2318528.html#a6452857 Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
