I could probably take a stab at Sharpen this weekend. I need to pull down
the java version of lucene anyways.
On Wed, Jan 5, 2011 at 1:50 AM, Prescott Nasser wrote:
>
> For number 2, you're spot on - free to the Lucene.Net project is probably
> the relevant piece. Someone mentioned having an open
Scripted, automated and repeatable are mantras to live by. Why not
take it all the way?
What I mean by this is setting up the new, fresh, Lucene 3.0 project
to do something like the following:
1) setup a CI server that grabs the current stable java source
automatically from SVN and runs our conve
Some ideas to pursue:
1) Get lucene into nuget. Given nuget has Microsoft's weight behind
it, it is going to become the defacto way people find .NET libraries.
This is relatively simple -- pretty much packaging the binaries with
an xml file. We could the current release in there today, and follow
Anyone else get the feeling that Java and C# are kind of like British
and American english -- two people separated by a nearly common
language?
As for inspiration, RavenDb might be a good place to start. It has
native Lucene querying capabilities and the API is quite sexy and has
a number of good
