We might want to do a similar thing for Apache Maven Daemon, by the way. I think Daemon is still on 4.0.0-rc-3, which is even older.

It's been way too long since I cut Maven releases (and I think I never ever cut a release of Core) so I'm a bit hesitant to step up and offer to do it myself. I'll be more than happy to test-drive any new RC's though!


Maarten

On 16/10/2025 11:04, Maarten Mulders wrote:
Absolutely no objections, I would very much like to see 4.0.0 happen!

Would it make sense to cut a 4.0.0-rc-5 release with the aim of gathering feedback, and the promise of "this will be 4.0.0 if no major issues are found"?

One way or another, thanks for stepping forward and taking the initiative. Also big thanks for everyone who contributed in small or in large to getting this far!


Maarten

On 15/10/2025 20:42, Guillaume Nodet wrote:
Hey everyone,

We've fixed a ton of issues on the 4.0.x branch [1], so I think it’s time
to cut the 4.0.0 release.
Before that, I’d just like to get the Spotless/Palantir plugin upgraded [2]
so that it works properly on JDK 17, 21, and 25 (we can later bump to the
upcoming parent once it includes the same change).

The release notes [1] currently only show the diffs since RC4, so we should
probably do another pass on the “What’s New in Maven 4” page [3] — to
highlight the new mvnup upgrade tool (from rc-4) and double-check that
everything important is covered (if you see anything missing, please yell).

Any objections to this plan? If not, shall we go ahead?

Cheers,
Guillaume Nodet

[1]
https://github.com/apache/maven/releases/tag/ untagged-269a18e49ead47082a92
[2] https://github.com/apache/maven/pull/11275
[3] https://maven.apache.org/whatsnewinmaven4.html



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to