Re: [Lucene.Net] Lucene.Net 3 onwards and 2.9.4g

2011-12-28 Thread Christopher Currens
One of the benefits of moving forward with the conversion of the Java Lucene, is that they're using more recent versions of Java that support things like generics and enums, so the direct port is getting more and more like .NET, though not in all respects of course. I'm of the mind, though, that

Re: [Lucene.Net] Merge 3.0.3 into trunk and other forward progress

2011-12-28 Thread Rory Plaire
I'm not that proficient in JIRA yet, and can only find 22 open issues outstanding. Is this correct, or am I missing something? -r On Fri, Dec 23, 2011 at 2:38 PM, Prescott Nasser geobmx...@hotmail.comwrote: You can look at the jira issues for Java lucene 3.0.3 and submit patches for 2.9.4g

RE: [Lucene.Net] Lucene.Net 3 onwards and 2.9.4g

2011-12-28 Thread Digy
but I guess the future of 2.9.4g depends on the extent that it is becoming more .NET like My intention while I was creating that branch was just to make 2.9.4 a little bit more .Net like(+ maybe some performance). I used many codes from 3.0.3 Java. So it is somewhere between 2.9.4 3.0.3 But I

RE: [Lucene.Net] Merge 3.0.3 into trunk and other forward progress

2011-12-28 Thread Prescott Nasser
That's 40 issues that the Java Lucene team tagged as needed for 3.0.3 release (so they are all closed atm) I will try to port many/most of these over this week into our JIRA so we can track them for ourselves. From: geobmx...@hotmail.com To:

RE: [Lucene.Net] Lucene.Net 3 onwards and 2.9.4g

2011-12-28 Thread Prescott Nasser
Any reason we can't continue this g branch and make it more and more .net like? I was thinking about what we've expressed at goals - we want a line by line port - it's easy to maintain parity with java and easy to compare. We also want a more .NET version - the g branch gets this started -