Michael, I do not agree. As a user and maintainer of the build chain in my company, I think Maven would really benefit from an out of the box solution. I think any user is susceptible to the bug by launching multiple Maven instances at the same time on his computer. Bugs then encountered are really a bad sign sent to users, and requiring each dev to setup a database (even simple) is cumbersome.
Regards François Le lun. 4 oct. 2021 à 22:13, Michael Osipov <micha...@apache.org> a écrit : > Tamás, > > Redis is so easy to install and get going in 5 minutes that I would > rather see your energy go into areas which need more attention. > > M > > Am 2021-10-04 um 22:02 schrieb Tamás Cservenák: > > Hi Bernd, > > > > nothing is wrong with advisory file locking, as long as you don't store > > local repo on NFS ;) > > Will re-add file locking once I get there, as in my opinion it is the > most > > "lightweight" MP (multi process) solution on a single host. > > Redis and Hazelcast are more for "farms", where several hosts with many > > processes (and each with many threads) is bashing local repo (that MAY be > > on NFS as well). > > > > Thanks > > Tamas > > > > On Mon, Oct 4, 2021 at 9:37 PM Bernd Eckenfels <e...@zusammenkunft.net> > > wrote: > > > >> What’s the problem with adivisory locking, as long as Maven honors the > >> advice it is the same as it’s a redis lock? (But much less footprint). > In > >> fact on the same machine it should even work without locking as Long as > you > >> use pidfiles? > >> > >> Gruss > >> Bernd > >> > >> > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
