No one ever told me about this convention and I knew about it the
moment I saw the version numbers.
However, Elliote is right, that's not semver.
The alternative would be to put a lookup / compatibility  table in
each plugin's readme. But that would be so annoying as a user, because
Maven is just SO modular!

+1 for keeping the 3.x.x numbers. I think everyone knows about it by now.

Am Fr., 10. März 2023 um 18:52 Uhr schrieb Tamás Cservenák
<ta...@cservenak.net>:
>
> Howdy,
>
> Sure, am fine, but from history:
> Maven1 had 1,x plugins.
> Then Maven2 was fully rewritten, and all plugins became 2.x (despite there
> was no "backward compatibility", as Maven1 plugin could never run in Maven2.
> Then Maven3 was done with full backward compatibility as one of the goals,
> hence things like default lifecycle carried for quite a long time 2.x
> plugins, while 3.x plugins existed as well (even same ones). Simply put,
> 2.x plugin broadly spoken "uses Maven2 API" and works in both Maven2 and
> Maven3 (due it's bw maven-compat), but a 3.x plugin could NOT work in
> Maven2, only in Maven3.
>
> This was always true for core plugins. Mojohause and 3rd party plugins
> never followed this scheme sadly.
>
> So, something like this was envisioned:
> https://gist.github.com/cstamas/b0605a9fad09de4adcbd4444888baa4c
>
> T
>
>
>
> On Fri, Mar 10, 2023 at 6:37 PM Michael Osipov <micha...@apache.org> wrote:
>
> > Am 2023-03-10 um 18:31 schrieb Tamás Cservenák:
> > > Maven plugin cannot have a new major version, as "by convention" it would
> > > mean it requires Maven 4 to run.
> > > As in this case it would be m-remote-resources-p 4.0.0 (as currently it
> > is
> > > 3.x,x).
> >
> > That's is not necessarily correct. Working on Doxia 2 I have bumped all
> > reporting plugins to next major in a branch to reflect the breaking
> > changes. Just requires proper docs, IMHO.
> >
> > M
> >
> >

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to