Re: Strategies for automatically fixing local maven repo corruption?

2022-03-23 Thread Bernd Eckenfels
You should avoid concurrent builds on a local Repo. Either use a “per worker” Repo (all good CI servers should support that, but you can also do it by hand command line option) or use a Container build process. There is also a locking scheme for Maven now, but I would start with Seperate

RE: Strategies for automatically fixing local maven repo corruption?

2022-03-23 Thread Jacques Etienne Beaudet
You're right sorry about that https://svn.apache.org/repos/asf/maven/website/components/resolver-archives/resolver-1.6.3/maven-resolver-synccontext-redisson/index.html On Mar 23, 2022, 6:28 PM -0400, KARR, DAVID , wrote: > > -Original Message- > > From: Jacques Etienne Beaudet > > Sent:

RE: Strategies for automatically fixing local maven repo corruption?

2022-03-23 Thread KARR, DAVID
> -Original Message- > From: Jacques Etienne Beaudet > Sent: Wednesday, March 23, 2022 3:14 PM > To: Maven Users List > Subject: Re: Strategies for automatically fixing local maven repo > corruption? > > I'll copy paste something I wrote in another thread but yea basically > there's a

Re: Strategies for automatically fixing local maven repo corruption?

2022-03-23 Thread Jacques Etienne Beaudet
I'll copy paste something I wrote in another thread but yea basically there's a neat way to help with this : Just chiming in on my experience using the redis locks with maven 3.8.x and resolver 1.6. I've been running it on my Jenkins nodes for about a year now with great success. Before it, we

Strategies for automatically fixing local maven repo corruption?

2022-03-23 Thread David Karr
Our enterprise has builds for a couple of hundred services running many times a day, on a set of Jenkins build nodes, most of which are Maven builds.The builds use a settings.xml that doesn't override the "localRepository", so it will use a local repository on the build node that is used by all

RE: What steps will install dependent artifacts in local maven repo

2022-03-23 Thread KARR, DAVID
> -Original Message- > From: Thomas Broyer > Sent: Wednesday, March 23, 2022 6:59 AM > To: Maven Users List > Subject: Re: What steps will install dependent artifacts in local maven > repo > > Releases are "immutable" in a Maven repository (or at least are expected > to be, and the

Re: What steps will install dependent artifacts in local maven repo

2022-03-23 Thread Thomas Broyer
Releases are "immutable" in a Maven repository (or at least are expected to be, and the Central Repository enforces it), so if 3.7.1 is compatible with JDK 8, it will stay that way. On Wed, Mar 23, 2022 at 2:40 PM KARR, DAVID wrote: > Inline. > > > -Original Message- > > From: Alexander

RE: What steps will install dependent artifacts in local maven repo

2022-03-23 Thread KARR, DAVID
Inline. > -Original Message- > From: Alexander Kriegisch > Sent: Wednesday, March 23, 2022 1:11 AM > To: users@maven.apache.org > Subject: Re: What steps will install dependent artifacts in local maven > repo > > Some background information, because I happen to know, being an AspectJ >

Re: What steps will install dependent artifacts in local maven repo

2022-03-23 Thread Alexander Kriegisch
Some background information, because I happen to know, being an AspectJ committer and the AspectJ compiler being a fork of ECJ, just like GrEclipse is, too: The JDT Core project has decided a while ago - I think for the Eclipse 4.22 (2021-12) release, maybe one release earlier - to drop Java 8