I checked what it would take to test all of the javadocs on trunk, and found
that there is no one target to call. To cover all javadocs:
cd lucene ; ant javadocs-all javadocs-test-framework
cd ../modules ; ant javadocs
cd ../solr ; ant javadoc-all javadoc-test-framework
Ideally, the javadocs would be generated once under 1.5 and again under 1.6,
for all of branch_3x, and for lucene/ & modules/ on trunk.
I got a bunch of javadoc warnings in Solr, so (assuming I don't have setup
issues) some work needs to be done to fix the warnings before bombarding
everybody with failure messages every 30 minutes.
I assume the branch_3x issues are similar, but I haven't looked into it yet.
Steve
> -----Original Message-----
> From: Michael McCandless [mailto:luc...@mikemccandless.com]
> Sent: Sunday, May 29, 2011 8:48 AM
> To: dev@lucene.apache.org Dev
> Subject: do the Jenkins while(true) builds now catch javadoc warnings...?
>
> I know we discussed that this was an easy fix to the shell script...
> but did anyone make the change?
>
> Ie, so that we catch JS warnings in the while(true) build, not just
> nightly/POM builds.
>
> Mike
>
> http://blog.mikemccandless.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
