I'm wondering about the size of the builds, which are surprisingly big to me. The src is 12M/13M and the bin is 17M/26M (tar.gz/zip) for 2.9.1, similar for 3.0.0.
In looking at the binary artifact I see the following: * Every contrib jar has a corresponding javadoc jar, but there is no core-javadoc.jar, however, there is a doc folder that is not jarred and it has all the contrib documents in it. Is it really needed to include it in the bin at all? In my working environment, Eclipse, they are entirely unnecessary when one has the src.zip. I imagine that other IDEs are similar. And they are trivial to generate. I'd rather see a separate JavaDoc tar.gz/zip. And if it is needed in the bin artifact, is it necessary to have it uncompressed and partially duplicated? The contrib javadoc.jars total 4.3M and the docs/api when zipped or jarred has a size of 13.7M. For whatever reason, gzip is much better at compressing javadoc than zip or jar is. While not duplicating the contrib javadocs would be better, not jarring the contrib javadocs would improve the gzip compressibility for bin artifact and not adversely affect the size of the zip. * There is a src folder that has a few things in it. Aren't these in another jar? And shouldn't they folder not be there? After all it is not a src artifact. * The lib folder has the servlet-api-2.4.jar in it, but the junit-3.8.2.jar is not. Should either of these be there? Regarding the src artifact I see the following: * It is far more than the src for the bin artifact. ** It includes site files. ** It includes tests. ** It includes 3-rd party jars for contrib. 6.3M of them. I get that it is merely an export of SVN, but should it be? Could it be broken out into separate parts? Would that make sense? E.g. lucene-src -- Contains the parts for the bin jar. lucene-test -- Contains the tests. lucene-dependency -- Contains the 3-rd party jars. lucene-misc -- Contains the site files and miscellaneous other stuff. Regarding the 3-rd party jars, there are 2 jars that are not in svn that lucene/contrib requires and to get them one has to bootstrap by running ant. These are the bdb libs. I also see that lucene has a patched Xerces (is that still necessary?) and a custom build of ICU4J (are there instructions for creating that? I didn't find them.). Every release of Lucene, I find my self repackaging the bin and src to skinny it down to what we need for our development environment. That's my motivation for raising these questions. If we can figure out if or what should change, I'd be glad to do the ant work. I know enough of ant to be dangerous ;) -- DM --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
