And a short addendum: Given, today there are still no Maven 4.x plugins nor Doxia 2.x reports out there (released), what if, we follow Michael intent BUT with a slight "bend": - the new Maven Site plugin that uses Doxia 2.0.0 and would carry version 4.0.0 (to be released) **should be Maven4 plugin** - this implies that all reports stuff that will Doxia 2.0.0 MUST BE Maven4 plugins as well - basically, leave Doxia 1.x for Maven3 as is, and use Doxia 2.x for Maven4
T On Fri, Mar 8, 2024 at 12:20 PM Tamás Cservenák <ta...@cservenak.net> wrote: > Just to clarify, explain myself but also FTR on thread: > > in case of report-plugins we basically have TWO requirements (or deps): > - maven API level > - doxia API level (that with 2.0.0 contains breaking changes) > > Basically, Maven4 supports 4.x plugins (that use new API) but also > supports running 3,x plugins (in "compat" mode, just like today, as there > are still no 4.x plugins out there). > But Doxia introduces hard breakage, as far as I understand (correct me > here if I am wrong), there is no "Doxia 2.x backward compat support for > Doxia 1.x clients"? > > Given Doxia 1.x is being phased out, and unlike for Maven API (where we do > want and will maintain 3.x and 4.x plugin versions in parallel), this is > not happening with reports/doxia. > We do not want any Doxia 1.x report to be released, right? > > This also implies that a build that does use reports, cannot "gradually" > migrate to Doxia 2.0.0, no? > It is all or nothing, no? So either a new site plugin with Doxia 2.x or an > old site plugin with Doxia 1.x? > > T > > On Fri, Mar 8, 2024 at 11:50 AM Tamás Cservenák <ta...@cservenak.net> > wrote: > >> Howdy, >> >> First, 4.0 is not out yet (check my remark in the initial mail "M >> releases do not count"). >> >> Second, is there a plugin out there that also includes a report? >> (or in other words, you remember I was insisting to SPLIT OUT all the >> report stuff out of plugins) >> >> As if there is no such plugin, we deal with them just like explained >> above in case of "breaking changes": >> basically report-plugins will have breaking changes and will require new >> site stuff... >> >> If there is a plugin that includes report as well, report MUST be >> split out as the first step. >> >> T >> >> On Fri, Mar 8, 2024 at 11:29 AM Michael Osipov <micha...@apache.org> >> wrote: >> >>> Am 2024-03-08 um 11:19 schrieb Tamás Cservenák: >>> > So, can we agree on following (maybe even vote if needed)? >>> > >>> > I. Core Plugin Versioning >>> > Maven3 plugins carry 3.x as the major version number, and Maven4 >>> plugins >>> > will carry 4.x major versions? >>> >>> See Maven Site Plugin 4.0, contains fundemantal changes in the >>> background, cannot keep 3.x. Same will apply to almost all of our >>> reporting plugins which is caused by Doxia 2.0.0. Totally unrelated to >>> Maven 4. How do deal with that? >>> >>> M >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >>> For additional commands, e-mail: dev-h...@maven.apache.org >>> >>
