Think site got slowly replaced by other alternatives - even to document mojos! - so today it is mainly about us and I also dont think limiting doxia 2 to maven 4 has much issues, there is no real request from outside for it AFAIK.
>From a versioning standpoint I see really no reason to make a transitive dep surfacing in a mojo, here it just highlights the site plugin is not selfcontained as it should maybe be so maybe mvn4 could revisit it and try to make our site integration back usbale by some users. So I really see no reason to shout ourself in the foot for a single case which is ultimately promished to more real redesign if we want to keep it on the long run. So let's start simple and if some users want it we'll sort it out as we already did in some plugins which were multi versions friendly...but had a single version if you follow ;). Le ven. 8 mars 2024 à 21:18, Michael Osipov <micha...@apache.org> a écrit : > I plan to publish an announcement *before* I update anything or bump > reporting plugins to the (now) next minor version. People will always > complain -- regardless of what you do -- if they are unhappy. > I don't expect you to waste to time for site, just skip it mentally. I > will take care. > > Am 2024-03-08 um 21:10 schrieb Tamás Cservenák: > > Michael, > > > > I understand, but then all that remains is +10 or +100 in versions, > > trickeries, or whatever... > > > > Be prepared for "this works with that but does not with that other" types > > of JIRA... > > And my guess is that the few who still use the site function of Maven > will > > simply drop it. > > A big confusion is ahead, but I'd really not waste any (my at least) > energy > > on "what works with that in site" type of thing. > > > > This reminds me of Smylex, from Batman (1984). > > > > T > > > > > > On Fri, Mar 8, 2024 at 9:01 PM Michael Osipov <micha...@apache.org> > wrote: > > > >> Am 2024-03-08 um 20:56 schrieb Tamás Cservenák: > >>> I agree with Gary, > >>> > >>> really really the simplest would be to NOT use Doxia 2 for Maven 3, as > >>> basically that IS the "plugin breakage" we are soon facing. > >> > >> This is unacceptable for me because that breaks two years of ongoing > >> effort. I cannot expect people to move off Maven 3 because of site > >> generation. This is not a core issue since reporting has been removed > >> from Maven Core in Maven 3 for good. Please DO NOT conflate what has > >> been untangled 10+ years ago. I can/will use a minor release with a > >> special section in the release notes since next major is unvailable. > >> > >> M > >> > > > >
