Mailing-List: contact user-help@uima.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@uima.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <4DA5904F.7060305@uni-jena.de>
Date: Wed, 13 Apr 2011 14:00:15 +0200
From: =?ISO-8859-15?Q?Erik_F=E4=DFler?= <erik.faessler@uni-jena.de>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de;
 rv:1.9.2.9) Gecko/20100914 SUSE/3.1.4 Thunderbird/3.1.4
MIME-Version: 1.0
To: user@uima.apache.org
Subject: Sandbox: LuCas Lucene update
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit

  Hey all,

back in January, I had the need to have the CAS Lucene indexer (LuCas, 
UIMA Sandbox component) working with Lucene 2.9.x. So I checked it out 
from the Sandbox SVN, updated the libraries and fixed the compiling 
bugs. The result is a LuCas component working with Lucene 2.9.3. At 
least all tests are working and I used the component (together with Solr 
which was why I needed Lucene 2.9.x) successfully.
The changes needed were not too big as I did not take the leap to Lucene 
3.x. Some filters have been updated to the new Token API and one or two 
classes required a more or less complete rewrite until the tests would 
work again.

So, my question: Would it be desirable to commit these changes back to 
the Sandbox SVN? Which steps would have I have to take for this? Or 
should I just send my sources to a developer? The component has been 
created in my lab originally, but the developer has moved to another 
working place quite a while ago.

Best regards,

     Erik