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]
