Maarten, that would need a LOT of work, from maven plugin tools, IDEs and ALL the stuff that _assumes_ that a plugin artifactId is either "maven-xxx-plugin" or "xxx-maven-plugin". Never looked into, but I guess that would be quite a big impact.
T On Fri, Mar 8, 2024 at 8:22 PM Maarten Mulders <mthmuld...@apache.org> wrote: > It might've been proposed and rejected before, but how about > > 1. maven4-compiler-plugin > > -or- > > 2. maven-compiler-plugin (with maven4/maven5/etc classifier) > > In both scenario's, we could still use semantic versioning as we do > right now, and as Maven users probably expect us to adhere to. > > Thanks, > > > Maarten > > On 08/03/2024 20:10, Michael Osipov wrote: > > Am 2024-03-08 um 17:20 schrieb Guillaume Nodet: > >> I'm slightly hesitant about that. > >> It seems to me plugins have mostly been compatible, so we very rarely > >> used a major version switch, but we do have plugins in 3.12.1 for > >> example, which would be translated to 3.0.12.1. Not even sure how the > >> 4th digit is supported... > >> I wonder if an alternative proposal would be to do a 10 unit big jump > >> in the minor version to represent a breaking change, so from 3.12.1 to > >> 3.23.0.... > > > > A four number system would contradict our approach. I guess a ceil to > > the next 10 minor version is OK for that. So MSITE would be 3.20.x. > > Applies to all reporting plugins as well and major will stay at 3. > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
