Hi Everyone, Two other things:
1) Beside the exception during optimization, there are a number of porting questions that I have. Just search for the text "Aroush-2.1" and you will find them. Beside those, there are left over porting questions, so it's best if you search for "Aroush". 2) Any fix that you provide, should be targeted at fixing the port and no more. That is, lets hold off any .NET 2.0 related changes till when we get this release working. Regards, -- George > -----Original Message----- > From: George Aroush [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 01, 2007 3:01 PM > To: [EMAIL PROTECTED]; > [email protected] > Subject: Apache Lucene.Net 2.1 build 001 "early-Alpha" is released > > Hi Everyone, > > I just finished checking in what is a first cut at Apache > Lucene.Net 2.1 release. This is as a result of porting Java > Lucene 2.1 to Lucene.Net. > > This release is a work in progress and here is a brief high > level summary of > it: > > - Dev Release: Apache Lucene.Net.2.1 build 001 "early-Alpha" > - Issues: Optimizing an index will cause an exception. > - Issues: The "Test" code has not yet be ported for > this release. > - Issues: Code in "contrib" have not been validated to > work with this release. > > While I work on porting the "Test" code from Java Lucene to > Lucene.Net, please take a look at this release, test it, > report issues and most of all submit fixes in form of > patches. For starters, index optimization is causing an > exception. Anyone who can look at this issue is greatly appreciated. > > Regards, > > -- George Aroush >
