+1 here.
For the lucene part I tested the following:
* md5 signatures:
for i in *md5; do; md5sum -c $i; done
lucene-3.5.0-src.tgz: OK
lucene-3.5.0.tgz: OK
lucene-3.5.0.zip: OK
* compare the size of tgz and zip extractions
* ant: clean + test + javadocs targets - all passed
* move one of my projects to use 3.5.0 - had to modify some code due to
(documented) API changes - all compiles and all tests passed.
* there are 55 jars in each of the packs, each code jar has a javadoc jar,
except for lucene-facet-3.5.0-examples.jar, which is ok, but it might
expose an issue here:
** what really is of value here are the example sources, so I wonder if for
example code like this, sources should be included with the jar, or perhaps
a separate jar with the sources should be packed.
** Perhaps, similarly, this also holds for lucene-demo-3.5.0.jar, where
users would like to have the source code of that demo, even if just
downloading the binary release.
If agreed to fix these it should be for future releases and is not a
release stopper.
