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
I think for Solr it's actually ant javadocs (confusingly!). This
seems to subsume javadoc-all?
Also, I don't think I'm getting javadoc warnings for Solr? (I do get
lots of compilation warnings). If you introduce a javadoc warning it
fails the build...
I agree it'd be great if we could gen the
OK I think this should do it? I'll commit shortly if nobody objects...:
Index: hudson-lusolr-tests-trunk.sh
===
--- hudson-lusolr-tests-trunk.sh(revision 1128882)
+++ hudson-lusolr-tests-trunk.sh(working copy)
@@
OK I committed that.
I also committed this, to hopefully fix the broken 3.x Maven build:
Index: hudson-lucene-solr-maven-3.x.sh
===
--- hudson-lucene-solr-maven-3.x.sh (revision 1128882)
+++ hudson-lucene-solr-maven-3.x.sh
