Hello, It is the other way around, there might be situations where one job relies on the installed artifacts from the other, in this case you would need a shared Repo. It is however bad style. In all other cases you can use a executor- or even workspace-local local repository if you have enough space.
The advantage of avoiding concurrent access is that you get less influences from one job to the other (especially if you work with snapshots or multiple different upstream artifacts with same version in different Repos) and that there is no concurrent downloads (which in itself sometimes leads to checksum errors). Gruss Bernd -- http://bernd.eckenfels.net ________________________________ Von: Debraj Manna <subharaj.ma...@gmail.com> Gesendet: Montag, Mai 27, 2019 11:29 AM An: Maven Users List Betreff: Re: Maven local repo in a common global directory for multiple parallel execution Yes disk required will be more . I don't have a requirement where one of my projects requires artifact created by another. So I can use a common local repo for all parallel executions? On Mon, May 27, 2019 at 11:34 AM Golan, Yaron <yaron.go...@intl.att.com> wrote: > Please remember that you need much bigger disk space as you are > duplicating binaries. > > > -----Original Message----- > From: Debraj Manna <subharaj.ma...@gmail.com> > Sent: Sunday, May 26, 2019 4:49 PM > To: Maven Users List <users@maven.apache.org> > Subject: Maven local repo in a common global directory for multiple > parallel execution > > I have a machine in which multiple parallel maven execution happen . Each > execution executes the below command in a seperate workspace directory > > mvn -f main/pom.xml clean package -DskipTests -T 6 > > Can someone let me know should I use a seperate maven local repo path ( > -Dmaven.repo.local=$MAVEN_REPO) for each execution or I can use a common > .m2 directory for all parallel runs? What is the best practice? > > > - Maven Version 3.5 > - Java 8 >
