Thanks Nitin! I'm going to go ahead and fix all of the warnings and re-enable strict checking.
If anyone else has already started this, please let me know. -Kirk On Thu, Jan 28, 2016 at 11:10 AM, Nitin Lamba <[email protected]> wrote: > Yes, there is. > > To re-enable strict javadoc checking in JDK8, you can remove this command > line option present in build.gradle today: > > javadoc { > options.addStringOption('Xdoclint:none', '-quiet') > } > > Once it is removed, the build will fail. Last checked, it was generating > more than 100 errors! > > Nitin > > ________________________________________ > From: Kirk Lund <[email protected]> > Sent: Thursday, January 28, 2016 10:58 AM > To: [email protected] > Subject: Broken javadocs > > The build reports lots of broken javadocs. After fixing them, is there a > way (in gradle) to turn the warnings into errors that fail the build? I > would hate to go to all the effort of fixing these warnings and then see > people checkin more broken javadocs after that. > > Thanks, > Kirk >
