That's a good tip, thanks, but I didn't create any new package, so I don't think that's it. I did check all the (2) classes I added have javadocs, and the public methods that are not @Override
On Fri, Aug 6, 2021 at 1:03 PM Ilan Ginzburg <[email protected]> wrote: > > Did you create the javadoc package file? Usually its absence leads to cryptic > errors... > > On Fri, Aug 6, 2021 at 6:44 PM Michael Sokolov <[email protected]> wrote: >> >> Hi all, does anybody have helpful tips about how to chase down >> javadoc build failures? I made some new stuff, and ./gradlew test >> passes, but ./gradlew check fails with this less than fully >> explanatory message: >> >> $ JAVA_HOME=/usr/lib/jvm/java-1.11.0-openjdk-amd64/ ./gradlew check >> > Task :lucene:core:renderJavadoc FAILED >> >> FAILURE: Build failed with an exception. >> >> * Where: >> Script >> '/home/ANT.AMAZON.COM/sokolovm/workspace/lucene/gradle/documentation/render-javadoc.gradle' >> line: 450 >> >> * What went wrong: >> Execution failed for task ':lucene:core:renderJavadoc'. >> > No value present >> >> * Try: >> Run with --stacktrace option to get the stack trace. Run with --info >> or --debug option to get more log output. Run with --scan to get full >> insights. >> >> * Get more help at https://help.gradle.org >> >> BUILD FAILED in 3s >> 44 actionable tasks: 17 executed, 27 up-to-date >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
