On Wed, 14 Nov 2007, Pete wrote:
On Wednesday November 14 2007 12:29:09 pm Andi Vajda wrote:
The fix was in JCC proper. To take advantage of it, you need to rebuild JCC
first and then 'make compile install' one level above. 'make clean'
followed by 'make' also works, you'd just recompile the java code as well.
While these tools are evolving, perhaps it might make sense to record the
version number/SVN revision of JCC in modules it builds? I'm thinking
something analagous to the GCC info you get when you start python. Should
make bug reports easier.
JCC's setup.py has a version number, 1.2, which I changed when I made the fix.
You can verify that version number with the call below if you have setuptools
installed (which is the case by default on leopard, for example [1]):
> python -c "from pkg_resources import require; print require('jcc')[0]"
JCC 1.2
Andi..
[1] on Ubuntu Feisty or Gutsy you can install setuptools with:
sudo apt-get install python-setuptools
_______________________________________________
pylucene-dev mailing list
[email protected]
http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
