Another option is to completely remove our hosted project-wide javadoc and just crosslink to an external service like https://javadoc.io/doc/org.apache.jackrabbit. But from my perspective we should strive for hosting the javadoc ourselves… Konrad
> On 12. Oct 2023, at 11:46, Julian Reschke <[email protected]> wrote: > > On 12.10.2023 11:22, Julian Reschke wrote: >> On 12.10.2023 09:59, Konrad Windszus wrote: >>> Hi, >>> The published javadoc at >>> https://jackrabbit.apache.org/oak/docs/apidocs/overview-summary.html >>> is again outdated. It is from Oak 1.44 while the latest release is >>> 1.56.0. >>> Not sure if we need to rephrase point 9. from >>> https://jackrabbit.apache.org/jcr/creating-releases.html#part-ii-after-the-release-vote: >>> >>> "consider updating the live site” feels too fuzzy. For me this is a >>> mandatory step for stable releases. >>> WDYT? >>> Konrad >> >> Updating the site is not trivial as it requires a plugin that does not >> exist for Windows... >> >> Best regard, Julian > > What's worse is that the introduction of shaded-guava seems to have > broken the project-wide Javadoc generation. Will need to investigate. > > Best regards, Julian
