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 had corrupted local maven repos (zip file
empty kind of exceptions) a couple of times a week. Then, we
Maven repository is not safe when running multiple concurrent builds (not the
-T1C option). You need to use an external synchronization technique if you need
this.
https://maven.apache.org/resolver/maven-resolver-named-locks-redisson/index.html
Not sure of the implications of assuming an empty
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
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 Beaud
Exclusions are not yet supported at the dependencyManagement level. See
https://stackoverflow.com/questions/39276024/import-dependency-management-with-exclusion
for more informations or the corresponding unmerged PR
https://github.com/apache/maven/pull/295
Exclude it when you include the
Please see issue
https://issues.apache.org/jira/plugins/servlet/mobile#issue/MNG-4463 and will
be resolved in maven 4 if I'm not mistaken.
On Jul 27, 2022, 7:40 AM -0400, [Quipsy] Markus Karg , wrote:
> I think I found a bug in Maven, but I am not sure. Maybe I am doing something
> wrong, so
+1
On Feb 28, 2024 at 2:31 AM -0500, Benjamin Marwell , wrote:
> Hi Maven Devs/Users/Committers and PMC members!
>
> After several discussions on the mailing lists, I would like to
> start a vote in favour of setting the minimal Java bytecode target
> of Maven-Core 4 to 17 and hence require Java
