lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "George Aroush" <>
Subject RE: Lucene.Net 1.9 RC1 "final" is released
Date Tue, 11 Jul 2006 01:37:18 GMT
Hi Folks,

There is one more thing I originally wanted to add to my email below, but I
realized it may get lost in the long email, so here it is.

I want to take this opportunity and thank Peter Decrem who keep on bugging
me, validating and fixing the last set of remaining port issues in
Lucene.Net 1.9 -- at the very least, he kept me motivated and on my feet to
get this release out the door.  Many, MANY thanks Peter!

Now that work on 1.9.1 is about to start, I look forward for anyone who got
the cycles and can help with this effort.  Keep in mind, Lucene.Net needs
committers, so this is a great opportunity to become one, please see:


-- George

-----Original Message-----
From: George Aroush [] 
Sent: Monday, July 10, 2006 9:21 PM
Subject: Lucene.Net 1.9 RC1 "final" is released

Hi Folks,

I just released build 005 of Lucene.Net 1.9 -- which I am labeling as
"final".  With this release, all NUnit tests are now passing.

** For a list of what changed between build 004 and 005:

	- Release:  Lucene.Net.1.9 RC1 build 005 "final"
	- Fix: Lucene.Net.Search.MultiPhraseQuery.ToString() -- was skipping
one too many item during the iteration
	- Fix: Lucene.Net.Index.ParallelReader.GetFieldNames() -- was adding
the object instead of the dictionary value
	- Fix: Lucene.Net.Index.ParallelReader.Add() -- was adding the
object instead of the dictionary value
	- Fix: Lucene.Net.Store.Obtain() -- changed name from obtain() to
Obtain() (lower case to upper case)
	- Fix: Lucene.Net.Index.SegmentReader.~SegmentReader() -- removed:
	- Fix: Lucene.Net.Index.TermInfosReader.~TermInfosReader() --
removed: System.Threading.Thread.SetData()
	- Fix: Lucene.Net.Documents.DateField.DATE_LEN -- must use
SupportClass.Number.ToString() to get the length
	- Fix: Lucene.Net.Util.ToStringUtils.Boost() -- wasn't adding ".0"
when the value doesn't have a remainder
	- Fix: Lucene.Net.Index.SegmentReader.CreateFakeNorms() -- was
returning the wrong data member
	- Fix: Lucene.Net.Documents.NumberTools -- value of MIN_STRING_VALUE
and MAX_STRING_VALUE were wrong
	- Fix: Test.Lucene.Net.Analysis.TestISOLatin1AccentFilter.TestU() --
file was not saved as unicode; thanks to Ben Tregenna
	- Fix: Test.Lucene.Net.TestSearchForDuplicates.TestRun() -- wasn't
using MemoryStream correctly
	- Fix: Test.Lucene.Net.TestSearch.TestSearch_Renamed_Method() --
wasn't using MemoryStream correctly
	- Fix: Test.Lucene.Net.* -- replaced "[TestFixtureSetUp]" to
"[SetUp]" and "[FixtureTearDown]" to "[TearDown]"
	- Fix: Test.Lucene.Net.Index.TestParallelReader -- was comparing
objects instead of the dictionary value
	- Fix: Test.Lucene.Net.Index.TestSegmentReader -- was comparing
objects instead of the dictionary value
	- Fix: Test.Lucene.Net.Index.TestTermVectorWriter -- was not calling
	- Fix: Test.Lucene.Net.Analysis.Setup() -- was adding to the hash
without checking if the key already exist
	- Fix:
s -- all those needed their class member variables re-initialized

** For source access/download:

You can get a copy of the source off SVN from: (this is the
"tag" release, the dev release which in the next few days will become 1.9.1
is here: or
you can get a ZIP'ed of the source from:

** For online documentation access/download:

In addition to the source release, I have also released an online
documentation.  You can browse or download the online documentation from

** For general Lucene.Net information:

To learn more about Lucene.Net and get access to the code, documentation,
and mailing list, please visit:

Now that Lucene.Net 1.9 is out of our way, I have already started looking
into Lucene.Net 1.9.1.  The changes between 1.9 and 1.9.1 are not major, but
if you got cycles and can help we can get 1.9.1 out even sooner then I can
do all by myself.

Lucene.Net 1.9.1 will be targeted for .NET 1.1 and Lucene.Net 2.0 will be
targeted for .NET 2.0.  However, you can take the existing 1.9 release and
build it for .NET 2.0 with minor or no changes base on your need.  Also,
once Lucene.Net 1.9.1 is released, the move over to Lucene.Net 2.0 will be
just a mater of workspace changes -- thus, 1.9.1 is in a way 2.0.


-- George

View raw message