(NOTE: Moved to Solr Dev)
: It's not too bad (at least for solr-1.1.0, haven't looked at the
: upcoming 1.2.0 yet). To create the .deb, the java sources in the solr
...
: ant dist-war. The resulting .war-file is unpacked into the package file,
...
That sounds like a lot more work then just compiling/installing a "fat
war" containing all of the need jars embedded in it.
: > 3) Some of the jars Solr inlcudes in it's war are not the officially
: > released version of third party software. We frequently use development
: That may be a problem. For the depencies on Lucene, it may mean I should
: either wait for the next Lucene release before packaging the previous
: Solr release, or package a development Lucene release separately (I'm
: also one of the maintainers of the Debian Lucene package).
It's a moving target ... the APIs may change in between releases (ie: SOlr
could upgrade to a nightly build of Lucene between 2.1 and 2.2, and start
taking advantage of API changes made after 2.1 ... those APIs can freely
change again before the official Lucene 2.2 release. When Solr upgrades
it's embedded version to 2.2, we'll fix any breakage because of those
dependencies, but you may be screwed either way as long as you only look
at official releases of all the parties involved.
: The other libraries of which Solr uses unreleased versions (by the way,
: that are not noted in the README in the subversion repository, but I'm
: guessing from the jarfile names in lib/) are
we've never really had a policy of listing other third part jars that are
included in the README ... they're listed in NOTICES.txt
-Hoss
