On Mon, Sep 29, 2025 at 6:07 AM Romain Manni-Bucau <[email protected]> wrote:
> Le lun. 29 sept. 2025 à 14:51, Christoph Läubrich <[email protected]> a > écrit : > > > I think this thread really starts confusing. > > > > 1. surefire/failsafe is not part of maven so it can not be "dropped" > > from maven 4 > > > > You're partially right, let me add what was ambiguous: > - do not port surefire/failsafe to maven 4 api > That is not an option. If we start dropping plugins as part of the "3 -> 4 transition", most serious users will simply not move to 4. Your options are: - port everything to Maven 4. Make transitioning from 3 to 4 as painless as transitioning from 3.8 to 3.9. Or, better, 3.9.10 to 3.9.11. That will give you the most users for Maven 4. - do not port everything over. Some users will transition from 3 to 4 and eat up the pain of redoing their builds. The majority (and especially larger users) will - either remain on Maven 3 indefinitely. This is the best case scenario - look at the transition cost, ask themselves if they want to keep investing in Maven if the community pulls stunts like that or move to gradle. The gradle company will post case studies (and tools) to make Maven 3 -> gradle transitions simple. You lose your users. Maven 4 becomes irrelevant. Java is a mature ecosystem. Not a growing ecosystem. Unless there is an actual user base for Maven 4, there is no point of releasing it. You really do not want to split your user base at the most critical moment when you need them to trust and follow you across a major version transition (something we have not done in 20 (!) years). Once we managed to get users "over the hump" to Maven 4, we can talk about making some more substantial changes. Like in the 4.1 or 4.2 cycle. -h
