Re: [DISCUSSION] Apache Maven plugins versioning

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 as

Re: [DISCUSSION] Apache Maven plugins versioning

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, wrote: > Am 2023-03-26 um 19:02 schrieb Romain Manni-

Re: [DISCUSSION] Apache Maven plugins versioning

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! --

Re: [DISCUSSION] Apache Maven plugins versioning

@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. Romain Manni-Bucau @rmannibucau | Blog | Old Blog

Re: [DISCUSSION] Apache Maven plugins versioning

+1 to your proposal org.apache.maven:maven4-xyz-plugin: I don't think it would cause too much trouble as Maven APIs will love for a few years. It will only occasionally break when a new major Maven release is published. I can live with that. Also, maven 3 plugins will be compatible for a while.

Re: [DISCUSSION] Apache Maven plugins versioning

Am 2023-03-23 um 20:57 schrieb Slawomir Jaranowski: Hi, I know that historically plugin versions like 2.x was dedicated to Maven 2.x and versions 3.x is for Maven 3.x. We don't have any written documentation about it (or I can't find it), it looks like a traditional agreement. I wouldn't tie

Re: [DISCUSSION] Apache Maven plugins versioning

Hi We can also publish in plugin documentation history of Maven API and JDK requirements [1] I still think we should make some decisions on it ... and publish to be clear in such matters. We have m-site-p in version 4.0.0-M6 - does mean that should be used with Maven 4, it still require Maven 3.

Re: [DISCUSSION] Apache Maven plugins versioning

I vote +1 on just using semver, more or less, and calling it a day. We really shouldn't change artifact IDs unless we're changing everything else too so it's basically a new artifact. Even if it is a completely new plugin, it's likely that in the future it will want to support Maven 5+ so let's no

Re: [DISCUSSION] Apache Maven plugins versioning

Hi, Think linking maven and maven plugins version does not make sense for most people since at the end the compat is somehow documented by the dependencyso using a more common versioning (semver or not) sounds straight forward. What would be very bad for me would be a renaming (xxx -> xxx4 for ex)

[DISCUSSION] Apache Maven plugins versioning

Hi, I know that historically plugin versions like 2.x was dedicated to Maven 2.x and versions 3.x is for Maven 3.x. We don't have any written documentation about it (or I can't find it), it looks like a traditional agreement. Nowadays Semantic Versioning is very popular and it is understood by p