Howdy,
Resolver was affected, but UT code only (both, 1.9.x and master), the
affected UT was the same on both branches.
In short, the UT used `new File("")` in some stub, relying that test
cleanup will not act up (it did not before Java 25).
Details in the commits below.
Commits are pretty much (aligned GH CI and fixed UT):
https://github.com/apache/maven-resolver/commit/3af2e421b596b5a70c469fca5b78feb8a525c417
https://github.com/apache/maven-resolver/commit/cf89daa2c664f0b4da732417e84a9d1c0de85570
Thanks
T
On Tue, Nov 18, 2025 at 8:03 AM Hervé Boutemy
<[email protected]> wrote:
>
> thank you Sylwester for the post-mortem :)
>
> in 2 years, for JDK 29, we'll have to remember this experience and plan tests
>
> for Maven 4,we'll have such updates much more frequently: I'm interested into
> knowing which plugins / branches broke, as I suppose this can also help us
> have common return on experience on new Maven 4 releases
>
> do you remember a few cases where upgrading Maven 4.0-rc-4 to rc-5 broke
> something inside the Maven plugins ans components codebase?
>
> Regards,
>
> Hervé
>
> Le dimanche 16 novembre 2025, 13:26:10 CET Sylwester Lachiewicz a écrit :
> > Hi everyone,
> >
> > Recently, I opened and merged two pull requests related to Java 25 [1]
> > and the newly released Maven 4.0.0 rc5 [2].
> >
> > The first one replaced our well-known and stable Java 21 setup in CI
> > with Java 25, which came out about a month ago.
> > Unfortunately, this change had a significant impact across all our
> > Maven Core projects—more than 100 shared libraries and plugins. This
> > caused some unpredictable failures on our main branches and affected
> > contributors’ work.
> > My apologies for the disruption.
> >
> > The second PR, upgrading to Maven 4 RC4, also introduced some
> > instability in a smaller subset of our plugins. In many cases, we
> > override the Maven runtime version per project to match the version
> > used in development.
> > Projects relying on the default configuration were affected as a result.
> >
> > Over the past few days, I reviewed all our GitHub Actions CI pipelines
> > and fixed numerous issues across the 3.x and 4.x Maven lines.
> > Everything is now back to green, with only two builds still pending known
> > fixes.
> >
> > I sincerely apologize for the trouble and inconvenience caused by the
> > unstable pipeline.
> > The key takeaway is that in the future, we should coordinate such
> > upgrades more carefully and avoid setting Java or Maven globally to
> > the latest versions.
> > Each maintainer should have the opportunity to test and prepare
> > updates at their own pace.
> >
> > Have a great weekend,
> > Sylwester
> >
> >
> > [1] https://github.com/apache/maven-gh-actions-shared/pull/202
> > [2] https://github.com/apache/maven-gh-actions-shared/pull/209
> >
> > ---------------------------------------------------------------------
> > 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]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
