Apache Maven 3.10.0 Release Notes
19 comments · 99% upvoted · source · other discussions
comments
[deleted]
lurker_in_spirit
Reproducible builds are now active by default, nice.
koflerdavid
Does anyone know what the default value is? (Please only answer if you happen to already know it; I'm just asking a lazy question)
[deleted]
[deleted]
koflerdavid
The documentation mentions that the timestamp will have a default value. I was wondering what exactly it is so I can decide whether it makes sense to remove it from my POMs.
persicsb
See https://issues.apache.org/jira/browse/MNG-8258 and the corresponding PR: https://github.com/apache/maven/pull/1726/files
It is 2001-01-01T00:00:00Z
koflerdavid
Thanks for indulging lazy me :-)
GermanBlackbot
Yay, they removed a few deprecated methods!
Oh no, this breaks some of my tests which relied on those methods!
I really need to fix my damn tests and move to integration tests for my plugins...
[deleted]
user_of_the_week 8 points · 25d ago
Yeah that’s also what I’m waiting on, for a long time now. Anyone know how to help? Do they need contributors? Or is it politics that’s slow?
tcservenak 5 points · 24d ago
Join us on mailing lists https://maven.apache.org/mailing-lists.html
Or just grab some issues from GitHub. Any help is welcome!
Mehis_ 7 points · 25d ago
According to a recent release, 4.0 will be released soon. I think they had a bunch of Maven API changes they wanted to do for 4.1. Let's hope it won't be long. :)
user_of_the_week 14 points · 25d ago
I understand delays happen, and I hope this doesn’t sound too entitled. Maven 4 has been “releasing soon” for years now.
Release candidate 1 came out in 2024!
Joram2 [OP] 5 points · 25d ago
I believe Maven 3.10 is a bridge release to smooth the transition to 4.0. Maven 3.10's main feature is that it's using the new Maven Resolver 2.x used by Maven 4.0 builds.
Inaldt 6 points · 25d ago
You're totally right of course, but I also think we have to cut them some slack. Maven is backed only by Apache, unlike the other big build tool, which usually means maintainers either need to do the work for free or for quite a limited compensation. So the people working on Maven - and I think there's only about a handful - probably have 'real' jobs next to it.
It's actually a bit (sort of) like the cliche that half the internet leans on a piece of software maintained by one guy is his spare time.
Either way. It seems they underestimated the amount of work. It's unfortunate but it's what happens in software. Until it goes GA, Maven 3 works just fine.
henk53 -1 points · 25d ago
Soon, those "real" jobs will only be burger flipping at night, until that too is replaced by AI?
nekokattt 3 points · 25d ago
This is something I'd be on board helping with, I've just struggled to find where to start after being on the CLA.
Xenogyst 0 points · 18d ago
As a casual observer of Maven for years, I don't think Maven 4's slow release is primarily a lack-of-contributors problem. It seems more like a consequence of an unusually conservative philosophy around stability and backward compatibility.
The first Maven 4 release candidate came out almost two years ago:
Where many engineers might accept that a major version introduces some incompatibilities, release it, and patch regressions as they're discovered, Maven seems to take a different approach.
The philosophy appears to be that Maven 4.0 must be safe for the existing ecosystem, rather than treating 4.0 as the beginning of a stabilization period. That means regressions in widely used plugins, builds, or downstream tooling can become release blockers. They've spent nearly (or more than?) two years working through compatibility issues, debating API contracts, and deciding what guarantees Maven 4 needs to make before GA.
There's a reasonable argument for that caution: Maven is foundational build infrastructure, and breaking it can have enormous downstream consequences. But there's also a cost to trying to establish that level of confidence before release.
And I don't think simply adding contributors would necessarily solve this. Open-source development doesn't scale linearly with headcount. Anyone who's worked on almost any software project knows that having 1,000 people submitting PRs doesn't automatically make development faster. Someone still has to review, integrate, coordinate, and make architectural decisions.
Maven seems less constrained by the number of people willing to contribute than by the difficulty of reaching agreement on what constitutes a stable major release.
Daggercombot 5 points · 24d ago
Oh that looks awesome,I cannot wait for that
[deleted] 2 points · 25d ago
[removed]
trydentIO 2 points · 25d ago
uuh! nice I didn't know about it!