I think we need to clarify that 1. Maven 3 plugins should work with Maven 4 (eventually require a recent update that fixes small compatibility issues), 2. and this is still the main expected way to use plugins with Maven 4
Maven 4 - specific plugins, using the still experimental Maven 4 API, is still a future thing in preparation in Maven 4.0.0 I suppose we can expect that Maven 4 API will further stabilize with Maven 4.1 And also clarify which Maven 3 plugins are definitively not compatible with Maven 4 and will absolutely require a Maven 4 specific one = know the exception to the norm I think that what I'm writing here is not wrong = why shipping as-is is adapted if there is stronger expectation on Maven 4 (plugin) API stability, good luck with the chicken and egg question given the wide ecosystem of plugins Regards, Hervé Le dimanche 25 mai 2025, 12:26:11 CEST Elliotte Rusty Harold a écrit : > On Sat, May 24, 2025 at 1:23 PM Guillaume Nodet <gno...@apache.org> wrote: > > I don't think they're talking about the Maven 4 API when they expect > > API stability. > > They rather refer to user-facing API such as schema changes, etc..., > > rather than dev-facing API. > > Plugin developers need API stability though. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
