It was part of the release process, which runs with Java 11. It should be fixed now.
> Newer java versions won't make a broken link, you just won't have a link at > all. This seems a bit of a shame, as some of the problems were genuine API bugs - public methods with package-private parameter classes, and so on. Do we have other ways of detecting these? Warning levels on the compiler maybe? > On 16 May 2022, at 18:14, Uwe Schindler <u...@thetaphi.de> wrote: > > Hi, > > Jenkins runs with JDK 11, so it should hit that problem. Was this in smoke > tester or during normal gradle build? > > Uwe > > ----- > Uwe Schindler > Achterdiek 19, D-28357 Bremen > https://www.thetaphi.de > eMail: u...@thetaphi.de > >> -----Original Message----- >> From: Robert Muir <rcm...@gmail.com> >> Sent: Monday, May 16, 2022 3:30 PM >> To: dev@lucene.apache.org >> Subject: Re: Lucene 9.2 release >> >> On Mon, May 16, 2022 at 9:28 AM Dawid Weiss <dawid.we...@gmail.com> >> wrote: >>> - different jvms producing different javadoc? Could this be the cause? >>> >> >> This is it, it is always a bug when javadoc produces broken links like >> this. It happens "at release time" because otherwise nobody is messing >> with java 11. >> >> Newer java versions won't make a broken link, you just won't have a link at >> all. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org >> For additional commands, e-mail: dev-h...@lucene.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
