Romain, You can look at this change (which I did, for plugin testing) just like resolver-1.9.x branch: a "stable" release of testing for 3.x plugins is very desperately needed. Same thing for maven-plugin-plugin. So yes, this is kinda the b) option: a Maven4 plugin cannot be built (m-p-p or tested m-p-t) with Maven3 tools and Maven3.
As for doing this for plugins (all of them) is open for debate. T On Mon, May 6, 2024 at 12:31 PM Romain Manni-Bucau <rmannibu...@gmail.com> wrote: > Hi Tamas, > > If the impact is to prevent to build a maven 3 (original setup version or > CI version for ex) with maven 4 (local version for ex) then I think it > violates the contract we had for maven 4 and I'd really like it to not > happen. > If it is the opposite (a maven 4 based/native project can't be ran with > maven 3) then +1. > What I'd really don't want to see is to have to maintain 2 branches for all > plugins for the coming ~5 years. > If *really* an issue I'd prefer we write a migration project (openrewrite > like - probably without openrewrite technically) to just write the maven 4 > project and make it maven 3 friendly automatically (can be a x-maven-plugin > downloading x-v3 or x-v4 subartifact for the runtime, not sexy internally > but very smooth in terms of usage). > > Best, > 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. 6 mai 2024 à 12:14, Tamás Cservenák <ta...@cservenak.net> a écrit > : > > > Howdy, > > > > my pain point was plugin-testing-harness 3.3.0 that is really ancient, > > while master of it was mixing maven3 and maven4 support... so I went to > > split things. > > > > IMO we need to split (like maven-3.x and master branch) for maven 3 and > > maven 4 support, as there is really no need to support "both", as in case > > of plugins, they are "this or that", they cannot be maven3 and maven4 at > > the same time. > > > > Hence, I started with maven-plugin-testing: > > https://github.com/apache/maven-plugin-testing/tree/maven-3.x > > > > Please eyeball and would like to prepare a 3.4.0 release of it soon. > > > > By the way, same should be done in maven-plugin-plugin (no need to > support > > creation of maven3 and maven4 plugins at the same time)... and maybe same > > pattern (using branches maven-3.x and master for 3 and 4) should be > applied > > to all plugins? > > > > Thanks > > T > > >
