An easy fix is to run maven with one local Repo cache per executor thread. Jenkins has a option for that. Alternatively run the whole build in a container with Repo overlay. (I wish Jenkins had more support to prepopulate those)
Gruss Bernd -- http://bernd.eckenfels.net ________________________________ Von: Austin Witt <[email protected]> Gesendet: Monday, October 4, 2021 5:27:28 PM An: Maven Users List <[email protected]> Betreff: Re: Global pre-installation of Maven extensions w/out ~/.m2/lib/ext Is it broken in that it doesn't actually solve the problem? Or broken in that it doesn't actually install correctly in Maven? Regardless, is there a solution you would recommend for solving the "many concurrent instances of Maven are running against the same local repository, and sometimes their file writes conflict" problem? On Sun, Oct 3, 2021 at 10:59 AM Michael Osipov <[email protected]> wrote: > Am 2021-09-29 um 21:18 schrieb Austin Witt: > > I wish to install a Maven extension - Takari's Concurrent Safe Local > > Repository extension ( > > > http://takari.io/book/30-team-maven.html#concurrent-safe-local-repository > ) > > - on a system such that it's picked up by all Maven runs. > > > > Don't! It is broken! Throw it away! > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
