On Wed, 15 Aug 2012, Roman Chyla wrote:
The full names make things easier and I would also think that the top
level 'java' package should be optional.
Many thanks from me too!
Cool, so the PyLucene 4.0 build is now using --use_full_names !
The long test and sample rewrite has begun....
Currently, only test/test_Analyzers.py passes. All other test and samples
remain to be ported to the new API and their imports fixed to fit the new
generated Python module tree that follows the Lucene java package tree.
Volunteers to help with this would be appreciated !
If you're stumped by a Lucene API change, check the detailed CHANGES.txt and
even more detailed MIGRATE.txt files for examples and instructions on how to
port to the new Lucene 4.0 API.
http://svn.apache.org/repos/asf/lucene/dev/branches/branch_4x/lucene/CHANGES.txt
http://svn.apache.org/repos/asf/lucene/dev/branches/branch_4x/lucene/MIGRATE.txt
If you have questions about how to express some of these things with
Python and JCC, please don't hesitate to ask here.
To avoid having multiple people working on the same files at the same time,
please send a brief message to the list that you're taking on a particular
test or directory of tests/samples.
Andi..
