Le sam. 14 févr. 2026 à 22:56, Martin Desruisseaux < [email protected]> a écrit :
> Le 14/02/2026 à 21:19, Romain Manni-Bucau a écrit : > > > Side note: while maven 5 itself could use JPMS for its api + core + > > resolver modules (and likely nothing else), the rest must not use JPMS > > by design and stay user friendly (extensions + plugins) > > It is a little bit off-topic, but just for information: I hope to > propose a full modularisation of Maven 5, including core and all > plugins. I have see in the past arguments saying that we cannot discover > plugins at runtime using JPMS. But this not true: it is just that the > way to do that is different (we need to use java.lang.ModuleLayer). > This is not the blocker, this part is easy, the blocker is that a lot of mojo will never embrace JPMS so we must run without JPMS at all extensions and plugins (doesnt mean we can't run a JPMS plugin, OSGi does it for ex, but means this must not be a requirement). > > Anyway, this is probably not a topic before a few years. > > Martin > >
