Requirements for javadocs vary between Lucene and Solr (and between packages) 
as far as I understand it.
 is for Lucene and there is a semi-equivalent at
 for Solr.


From: At: 04/13/18 03:56:17To:
Subject: Re: Precommit failures

It's happening to me too!  I added a /** anything */ comment on these two 
methods and the warning went away.  But we don't have rules about requiring 
comments on public methods (I thought)?
On Thu, Apr 12, 2018 at 8:51 PM Erick Erickson <> wrote:

I'm getting this precommit failure on a fresh clone of master:


     [echo] checking for broken html...

    [jtidy] Checking for broken html (such as invalid tags)...

   [delete] Deleting directory
     [echo] Checking for broken links...
     [exec] Crawl/parse...
     [exec] Verify...
     [echo] Checking for missing docs...
     [exec]   missing Methods: strictlyWithin-double-double-double-
     [exec]   missing Methods:
     [exec] Missing javadocs were found!

Anyone have a clue? I don't see Jenkins failures for this so maybe
it's just me somehow.


To unsubscribe, e-mail:
For additional commands, e-mail:

Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker
LinkedIn: | Book:

Reply via email to