On Wed, 21 Dec 2022 at 15:08, Gilles Sadowski <gillese...@gmail.com> wrote: > > Hello. > > Le mer. 21 déc. 2022 à 15:08, Alex Herbert <alex.d.herb...@gmail.com> a écrit > : > > > > On Wed, 21 Dec 2022 at 12:26, Gilles Sadowski <gillese...@gmail.com> wrote: > > > > > > Hello. > > > > > > Artefacts are available from Maven Central, distribution files > > > are available from the ASF server and "rel/..." tag was created > > > > Thanks. > > > > > The [Math] web is not up-to-date yet. > > > IIUC, a new module must be added that will aggregate the > > > Javadoc. As it is now, the link "Latest API docs", in the left > > > bar menu, will be dangling (because files are in the respective > > > "sub-modules"). > > > Should I do it from the "4.0-beta1-release" branch? Or is OK > > > to only update "master", and from there, regenerate the site? > > > > > > Most links to so-called "long-term" apidocs should be > > > removed (as nobody would ever need to look at how to use > > > unsupported code). [They are empty anyways, and nobody > > > has ever complained...] > > > Also, IMO, we don't need to keep "long-term" apidocs for this > > > release, since it's "beta". > > > > > > Shall I send the [ANNOUNCE] message now? > > > Or should it be delayed until the web site is fixed? > > > > Fixing the site should not take long. > > Hopefully not, but I won't have time to try and do it until much > later this evening (or tomorrow). > > > Adding the aggregate module > > should be a simple copy of what is in RNG or Numbers but just updated > > to add the correct modules to the pom. > > > > I would update on master > > If you have the opportunity to do it... :-)
I have pushed a version to master with a docs module. It required putting the junit-vintage dependency in each module that uses it. If it is in the parent pom then the old junit 4 code is included in the aggregate javadoc report. A second issue was that the aggregate report errored on bad javadoc (and broke the build) whereas the respective modules only output warnings. I do not know why this occurs. It was fixed by using -Xdoclint:none for the javadoc options to ignore javadoc errors and allow the aggregate report to build. To create the site for the 4.0-beta1 release still requires merging the release branch back into master. Alex --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
