Last week Lucene.Net 2.9.4 was released on the official site.
There is no official news feed for the project, so I’m just copying here the announcement from their homepage:
We finally got it out the door, it took a lot longer than we expected. However, we have a ton of bug fixes rolled into this release as well as a number of new features.
- Some of the bug fixes include: concurrency issues, mono compilation issues, and memory leaks.
- A lot of work has been done to clean up the code base, refactoring the code and project files, and providing build scripts
- A couple of new features: Search.Regex, Simple Faceted Search, and simple phrase analysis in the Fast Vector Highlighter
- Download it now on our downloads page
Just around the corner is a 2.9.4g release (early January), that has been substantially refactored and uses generics across the board.
And there is a Nuget Package
There are now 2 official nuget packages for Lucene.net:
- Lucene.net, which contains version 188.8.131.52 and is strongly named
- Lucene.net contrib, which contains also the various additional feature like highlighter, faceted search and so on
If you already got Lucene via the pre-existing Lucene package, I recommend you change the package reference to the package with id Lucene.Net. But even if you don’t, and just update your package, you will get a DEPRECATED warning, but for the moment you will still get the new Lucene.net package.
Don’t worry, there is not risk of getting confused: the old packages are well marked as deprecated when you search for Lucene
In the future we will probably release also a package with a quick start.
Getting hold of the package id was the most complicate part of the process, and for that I want to thank Phil Haack for granting us ownership of the old lucene id (which didn’t have any owner), Roger Knapp for granting us ownership of lucene.net and Michal Latoszek for the Lucene.Contrib id.
Also to the Nuget team with which I spent an hour chatting online on the nuget channel on jabbr.net: thank you for giving advises on which was the best way to handle the “deprecation” of a package id.
Republished from CodeClimber [4 clicks].
Read the original version here [1 clicks].