So simply put Maven is stopping support of plugins that have not been updated for about 9 years (Maven 3.1.0 is in 2 days 9 years old).
I say go for it. Niels On Wed, 13 Jul 2022, 15:54 Tamás Cservenák, <[email protected]> wrote: > Howdy, > > for starter, read comments on this PR: > https://github.com/apache/maven/pull/765 > > TL;DR > Intent of "experiment" was to warn those users who use Maven2 plugins ("old > plugins") with Maven3.9+. > Reasoning: Maven 3.9 is "taking turn" toward Maven4, and just like Maven3 > did support Maven2 plugins, Maven4 will support Maven3 plugins, > but supporting two major versions is too much for us, nor we have resources > for. > > My "definition" of "old plugins": > - is built against Maven API older than 3.1 (exclusive) > - depends on maven-compat of any released version > - (minor) was built using old tooling (m-plugin-p), hence scopes of maven > bits are not provided > > Clearly, we are targeting users who slacked even Maven3 upgrade, as they > use plugins built with/for/against Maven2. > > Also, I think we all agree that some proactive solution (like the PR, emit > warnings during build is needed) as otherwise, history will repeat, just > like it happened in the past: > we have crucial plugins not yet existing for Maven3 and majority of our > users are still using 2,x ("old") plugins of those: m-install-p, > m-deploy-p, etc. > > > T >
