On Sat, 2020-11-28 at 19:12 +0100, Michael Osipov wrote: > Am 2020-11-28 um 17:46 schrieb Oleg Kalnichevski: > > On Tue, 2020-11-24 at 21:23 +0100, Michael Osipov wrote: > > > >
... > > Hi Michael > > > > I have a proposal that works quite complimentary to what you have > > been > > doing: > > > > 1. during the release process we publish release specific reports > > to > > the maven repository as a separate artifact. Ex: `httpcore-4.4.14- > > reports.zip` > > > > I personally find only javadocs and clirr reports useful. The rest > > are > > pretty useless in my opinion but I am fine with including other > > reports > > as well. > > > > 2. The website project can pull those reports out of the maven > > repository and add those reports to the project web site content > > (most > > likely as sub-directories: httpcore-4.4.14-reports.zip -> > > http://hc.apache.org/httpcore-4.4.14/reports/) * > > > > 3. The process of website publishing is fully self-contained and > > independent of any individual release and release vote. Any number > > of > > released components can contribute their reports to the project > > website > > at any point of time. > > > > * this will likely require a custom Maven plugin which I am willing > > to > > build and if there is interest contribute to the Maven ecosystem. > > I need to think about that, but it sounds a bit convoluted > especially > because you'd upload stuff to Maven Central with zero benefit for > the > general audience. > Nowadays storage is cheap. And conceptually this is the _right_ thing to do. Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
