On Fri, Apr 15, 2011 at 19:39, Kristian Rosenvold <kristian.rosenv...@gmail.com> wrote: > > fr., 15.04.2011 kl. 11.54 -0400, skrev Sony Antony: >> Thank you Jason : >> If 3.x local repository is not safe for concurrent access, how does maven3 >> implement parallel builds ( -T switch ) >> ( maybe they decide on teh parallelism by making sure that there is no >> concurrent read/write access on teh repository *for the same* artifacts ? ) >> > > The first half you got right, there is no concurrent writes of the each > individual artifact "by design". > > When it comes to downloading from remote repositories it's all handled > by a common (singleton) service anyway.
This is only correct for one single instance of maven running, where multiple threads are downloading artifacts, isn't it? I guess the OP wanted to know wether it is safe to use Maven3 in a CI, where multiple processes download dependencies. To my understanding it is not safe, there was a patch for Maven2, if I remember right. Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ https://bitbucket.org/mfriedenhagen/ --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
