So you mean maven 5 will need to rename and rerelease all plugins even if they will be compatible thanks the policy versioning rule + new API? Npm and webpacks are not great rerefences since they don't aim at being stable as we intend. Look at javaee (before the jakarta big bang which broke this assumption): you can use v4 and run on v7 and several parts were not even re-released so not sure the related work is worth it.
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance> Le lun. 27 mars 2023 à 19:22, Benjamin Marwell <bmarw...@apache.org> a écrit : > The advantage is simple. > With "maven4" in the module name, you don't need a compatibility matrix on > every plugins homepage or readme. > > Just look at npm modules and webpack... Tables over tables... > > > > > On Sun, 26 Mar 2023, 19:29 Michael Osipov, <micha...@apache.org> wrote: > > > Am 2023-03-26 um 19:02 schrieb Romain Manni-Bucau: > > > @Benjamin what's the addtion of the "4" except looking weird after 1 > > > version since you use semver? It forces 2 changes instead of one > without > > > anything else explicit IMHO. > > > > I fully second that! > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > >
