Jetty is a good one as well: https://github.com/jetty/jetty.project
Gary On Wed, May 28, 2025, 08:55 Sergey Chernov <serega.mo...@gmail.com> wrote: > Guillaume, that's awesome. It's good that there is no rush with it. > Once I'll have insights, I'll share them. > > Xeno, the project I'm checking is private unfortunately. Also this can be > quite challenging to find a good Maven multi-module project as a reference > for performance testing and compatibility validations, as many of big > projects e.g. have flaky tests and other issues. > Some of the biggest that I've seen: > * https://github.com/quarkusio/quarkus (has lots of customizations in > .mvn/extensions.xml) > * https://github.com/apache/dubbo > * https://github.com/apache/hadoop > * https://github.com/apache/struts > * https://github.com/vaadin/flow and https://github.com/vaadin/framework > > > On Wed, May 28, 2025 at 2:16 PM Guillaume Nodet <gno...@apache.org> wrote: > > > After considering the concerns about API stability, plugin > > compatibility, and the performance issues reported by Sergey (4x > > slower in rc3), I agree with Sylwester, Benjamin, and Elliotte that we > > should opt for an rc4 to address these issues. My proposal is to > > release a final release candidate (rc4) soon, aiming for a General > > Availability (GA) release in September. Post rc4, I suggest creating a > > 4.0.x branch to start work on 4.1.0. For 4.1.0, we could introduce API > > changes like records and sequenced collections, as well as new > > features such as mixins, cascading profiles, server aliases, JDK 21 > > (still under discussion) and more.... > > > > The recent API changes for JPMS, as Martin noted, only affect the > > experimental API, so they shouldn’t block the release. On Matthias’s > > suggestion, enabling GitHub Issues across all repositories before the > > GA seems like a good idea to improve user feedback. Let’s focus on > > stabilizing rc4 and addressing performance bottlenecks, possibly > > exploring Martin’s O(N²) concerns with profiling, as Sergey offered. > > > > What do you think about this plan? > > > > On a side note, I created a few months ago a project to check Maven 4 > > compatibility with all Apache projects using Maven. The results for > > RC-3 can be found at > > https://github.com/gnodet/maven4-testing/issues/2812. Most of the > > errors are caused by the use of incompatible plugins (which needs to > > be updated) or incorrect POMs (as Maven 4 is more strict about a few > > things). What would be nice is a tool to integrate in the shell that > > would fix those known incompatibilities, so that users would have an > > easier migration path. And we could apply it to this project to make > > more green boxes. > > > > Le mer. 21 mai 2025 à 08:11, Guillaume Nodet <gno...@apache.org> a > écrit : > > > > > > Hey Maven Devs, > > > > > > We're gearing up to release a new version from the master branch. I'm > > thinking we should go for 4.0.0 instead of rc-4. What do you all think? > Any > > feedback or ideas on the versioning or release plan? Let’s hear it! > > > > > > Cheers, > > > > > > Guillaume > > > > > > > > > > > > -- > > ------------------------ > > Guillaume Nodet > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > >
