the scary number for analyzers might be a bit out of date. (hopefully most of) these were cleaned up with the contrib/analysis javadocs+test patch this morning.
On Tue, Aug 18, 2009 at 8:34 PM, Chris Hostetter<hossman_luc...@fucit.org> wrote: > > As a general rule: if the javadoc command generates a warning, it's a pretty > good indication that the resulting javadocs aren't going to look the way you > expect. (there may be lots of places where the javadocs look wrong and no > warning is logged -- but the reverse is almost never true) > > The other day, I went through all of the warnings produced by "ant > javadocs-core" and fixed the offending javadoc comments. It would be great > if each of the various defacto "contrib maintainers" (you know who you are) > could take a look at the warnings produced by each of the contribs. > > They're pretty easy to spot if you grep the raw console output from the > nightly builds for "[javadoc]" and "warning" ... > > hoss...@coaster:~$ curl -s > http://hudson.zones.apache.org/hudson/job/Lucene-trunk/922/consoleText | > grep "[javadoc]" | grep "warning" | perl -nle 'print $1 if > m{contrib/([^/]*)/}' | sort | uniq -c > 96 analyzers > 32 benchmark > 52 collation > 8 db > 32 fast-vector-highlighter > 32 highlighter > 24 memory > 40 queryparser > 8 regex > 52 remote > 8 snowball > 8 xml-query-parser > > > > > > -Hoss > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-dev-h...@lucene.apache.org > > -- Robert Muir rcm...@gmail.com --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
