On Tue, Oct 7, 2025 at 2:48 PM Olivier Lamy <[email protected]> wrote:
> The refactoring branch has already started the idea of simplifying > things by using only the JUnit Platform engine. > [...] > > Focusing now on modernising/simplifying the internal parts and > cleaning legacy code of Surefire/Failsafe is already a big step > forward. > This sounds like the right focus to me. Cleaning up inside, but allowing users during the maven 3 -> maven 4 transition to "simply upgrade to the latest version and things keep working" is the right call IMHO. More disruptive changes will require a proper deprecation/removal cycle and they can be done for a 4.1 or a 4.2 release. I disagree that evolving maven and the plugins this way will hold us off a "maven 5" version in the future. Moving from 4 to 5 will depend on developer availability and user acceptance. The more users and organizations adopt maven 4, the higher is the potential of finding organizations either sponsoring or employing maven developers. Romain, I get that you see this differently. As a consultant, I would also push for "changes, changes, new things" because that would be how I earn a living. As a developer (and maintainer) within an organization, I have interest in stability and predictability. Dropping two of the absolute core plugins that have been in maven for 20 (!) years is the opposite of that. -h
