This is going to be tough to answer because there are so many dependencies that to give the question enough context you'd almost have to ship us your machine.
So some questions for you; which are answered best by editing your original question:
- This is only about JCC errors? And pylucene is the goal but not part of the problem?
- What sort of thousands of errors did you handle yourself? No, I don't want 1000 answers, I'm wondering why it was so difficult for a supported platform.
- What version of JCC are you trying to build?
As a wild guess, this line from the JCC installation instructions seems like it could be quite relevant:
Adding the Java directories containing the necessary DLLs and to PATH is a must.
Added in response to comments:
You've gotten yourself into dependency hell for which remote answers are nearly impossible. Just looking at the sheer number of revisions you have to list to describe the work should give you an idea of how many things you have to coordinate.
It's unfortunate, and I've certainly been there myself a couple of times which is why I now do whatever I can to minimize the number of "just outa beta" versions software stacks.
On Ubuntu Lucid, I was able to
$ sudo apt-get install pylucene
$ python
Python 2.6.5 (r265:79063, Apr 16 2010, 13:09:56)
>>> import lucene
>>> dir(lucene)
['AbstractCollection', 'AbstractField', 'AbstractList', ...
But that's last year's PyLucene running on last year's Python. And I don't know lucene so I can't even confirm minimal operation, but presume it is a working PyLucene 2.3.1.
Good luck; you may find that you need to relax your requirements if you want to get it working and remain sane.