Zachary,
That is on its way in. Itamar said a few weeks ago he was planning on
getting polygon support into the spatial module (I am assuming that
this is the Geometry namespace). I'm unsure if it will make it into
the official 3.0.3 release or it if it will be pushed back into a
maintenance
and see if the change fixes anything.
Thanks,
Christopher
On Tue, Aug 14, 2012 at 8:21 AM, Christopher Currens
currens.ch...@gmail.com wrote:
It must be something we've missed, as we want to target medium trust
locations in the future. I can't think of anything off the top of my
head
Christopher Currens created LUCENENET-500:
-
Summary: Lucene fails to run in medium trust ASP.NET Application
Key: LUCENENET-500
URL: https://issues.apache.org/jira/browse/LUCENENET-500
Project
[
https://issues.apache.org/jira/browse/LUCENENET-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Currens resolved LUCENENET-500.
---
Resolution: Fixed
Issue was in the WeakKeyT class in WeakDictionary.cs
gave up before doing that. ;)
Is there any use cases where we need to garbage collect attributes
before the stream/attribute source is closed? Changing to a normal
dictionary seems like a quick fix.
// Simon
On 2012-08-14 17:21, Christopher Currens wrote:
It must be something we've
created a medium trust app domain
wasn't working. I had to create an ASP.NET project and give it medium
trust to repro. I'm sure there's a way to do it, though.
Thanks,
Christopher
On Tue, Aug 14, 2012 at 9:08 AM, Christopher Currens
currens.ch...@gmail.com wrote:
Inheriting from WeakReference
for the day job. It actually
provides intellisense for JS inheritance so life is good.
On Thu, Aug 9, 2012 at 1:43 AM, Christopher Currens currens.ch...@gmail.com
wrote:
It used to be that way. VS2012 is the first version that produces
backwards compatible projects *and* solutions. There's
See inline comments.
Thanks,
Christopher
On Wed, Aug 8, 2012 at 12:07 PM, Granroth, Neal V.
neal.granr...@thermofisher.com wrote:
I just pulled down the 3.0.3 branch from SVN and have encountered an
initial problem with the VisualStudio solution file Lucene.Net.Core.sln in
the VS2010
FYI - SVN has been updated with corrected VS2010 solutions and added VS2012
directory/solution files.
On Wed, Aug 8, 2012 at 1:12 PM, Christopher Currens currens.ch...@gmail.com
wrote:
See inline comments.
Thanks,
Christopher
On Wed, Aug 8, 2012 at 12:07 PM, Granroth, Neal V
Phone
From: Christopher Currens
Sent: 8/8/2012 1:35 PM
To: lucene-net-dev@lucene.apache.org
Subject: Re: Lucene.NET 3.0.3 Build issues
Thanks for the feedback. Let us know if you run into any more
issues/concerns.
Thanks,
Christopher
On Wed, Aug 8, 2012
the proj files the same.
On Wed, Aug 8, 2012 at 7:27 PM, Prescott Nasser geobmx...@hotmail.com
wrote:
Yes
Sent from my Windows Phone
From: Christopher Currens
Sent: 8/8/2012 4:22 PM
To: lucene-net-dev@lucene.apache.org
Subject: Re: Lucene.NET 3.0.3
Subject: Re: Outstanding issues for 3.0.3
From: ita...@code972.com
To: lucene-net-dev@lucene.apache.org
Go ahead with contrib and tests, ill resume with core and coordinate
further later
On Jul 27, 2012 7:04 PM, Christopher Currens
currens.ch...@gmail.com
wrote:
I've
on this?
On Wed, Aug 1, 2012 at 9:31 AM, Itamar Syn-Hershko ita...@code972.comwrote:
I agree
What about the spatial stuff? you guys want to wait for it?
On Wed, Aug 1, 2012 at 7:19 PM, Christopher Currens
currens.ch...@gmail.com
wrote:
I think that while it would be nice to get it done
Itamar,
Where do we stand on the clean up now? Is there anything in particular
that you're doing that you'd like help with? I have some free time today
and am eager to get this version released.
Thanks,
Christopher
On Sat, Jul 21, 2012 at 1:02 PM, Prescott Nasser geobmx...@hotmail.comwrote:
take a bit more
time, so it's really up to you guys (or we can open a vote for it).
On Fri, Jul 27, 2012 at 6:35 PM, Christopher Currens
currens.ch...@gmail.com wrote:
Itamar,
Where do we stand on the clean up now? Is there anything in particular
that you're doing that you'd like help
[
https://issues.apache.org/jira/browse/LUCENENET-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Currens resolved LUCENENET-480.
---
Resolution: Fixed
This should be fixed now, there was an issue
[
https://issues.apache.org/jira/browse/LUCENENET-421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13415388#comment-13415388
]
Christopher Currens commented on LUCENENET-421:
---
Jackie Wong, are you
[
https://issues.apache.org/jira/browse/LUCENENET-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Currens updated LUCENENET-480:
--
Fix Version/s: Lucene.Net 3.0.3
I'm merging it back into trunk now. I just
I've got it working, compiling and all test passing...The only caveat is
that I'm not sure the best way to multi-target. It doesn't really work on
a project level, so you'd have to create two separate projects, one for
.NET 4 and the other for 3.5. To aid me, I wrote a small tool that creates
I can set a different build target, but I can't set the actual framework to
3.5 without doing it for all build configurations. On top of that, 3.5
needs System.Core to be referenced, which is done automatically in .NET 4
(I'm not sure if MSBuild v4 does it automatically?). I did kinda get it
+1
On Sun, Jul 8, 2012 at 4:01 PM, Frank Yu fengj...@gmail.com wrote:
+1
On Sun, Jul 8, 2012 at 12:23 PM, Petersen, Robert rober...@buy.com
wrote:
+1
Sent from my iPhone
On Jul 8, 2012, at 12:22 PM, Stefan Bodewig bode...@apache.org
wrote:
On 2012-07-08, Prescott Nasser
[
https://issues.apache.org/jira/browse/LUCENENET-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Currens resolved LUCENENET-484.
---
Resolution: Fixed
Thanks for your help with all of these Luc. Thanks
[
https://issues.apache.org/jira/browse/LUCENENET-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Currens updated LUCENENET-484:
--
Description:
These tests will fail intermittently in Debug or Release mode
[
https://issues.apache.org/jira/browse/LUCENENET-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Currens resolved LUCENENET-493.
---
Resolution: Fixed
This should be fixed now. Added a test
[
https://issues.apache.org/jira/browse/LUCENENET-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Currens updated LUCENENET-436:
--
Affects Version/s: Lucene.Net 3.0.3
Fix Version/s
[
https://issues.apache.org/jira/browse/LUCENENET-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Currens updated LUCENENET-434:
--
Fix Version/s: (was: Lucene.Net 3.0.3)
Lucene.Net 3.5
[
https://issues.apache.org/jira/browse/LUCENENET-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Currens updated LUCENENET-467:
--
Fix Version/s: (was: Lucene.Net 3.0.3)
Lucene.Net 3.5
I want to discuss the outstanding issues blocking a 3.0.3 release. I've
already moved quite a few bugs to 3.5 that are too time-consuming or
require too many changes to the code. It's fairly obvious that we wouldn't
be able to finish them. Other more serious bugs, like the
culture-sensitivity
I wonder if it will still require IsolatedStorage. I would assume so?
However, I would think that would only require creating a Directory type
that used IsolatedStorage APIs, and added a check in FSDirectory.Open to
return one of those if it's running on WP8.
On Wed, Jun 20, 2012 at 10:47 AM,
[
https://issues.apache.org/jira/browse/LUCENENET-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13397690#comment-13397690
]
Christopher Currens commented on LUCENENET-480:
---
Regarding the sorted
[
https://issues.apache.org/jira/browse/LUCENENET-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13397164#comment-13397164
]
Christopher Currens commented on LUCENENET-480:
---
Change {{ISetT x = new
[
https://issues.apache.org/jira/browse/LUCENENET-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Currens resolved LUCENENET-495.
---
Resolution: Fixed
Use of DateTime.Now causes huge amount
[
https://issues.apache.org/jira/browse/LUCENENET-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Currens updated LUCENENET-493:
--
Attachment: UpdatedLocalizedTestCase.patch
I've updated LocalizedTestCase
[
https://issues.apache.org/jira/browse/LUCENENET-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13393610#comment-13393610
]
Christopher Currens commented on LUCENENET-480:
---
I would feel most
[
https://issues.apache.org/jira/browse/LUCENENET-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13393615#comment-13393615
]
Christopher Currens commented on LUCENENET-337:
---
I'm unsure about
[
https://issues.apache.org/jira/browse/LUCENENET-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13393624#comment-13393624
]
Christopher Currens commented on LUCENENET-495:
---
Yeah, I noticed that new
[
https://issues.apache.org/jira/browse/LUCENENET-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13393631#comment-13393631
]
Christopher Currens commented on LUCENENET-495:
---
I did fix the thread
It should have been removed and not just commented out. This should not be
obsolete in this case, because it's inheriting from System.IO.TextReader,
and it's not obsoleted in the BCL. Any Close() defined in the Lucene.NET
library should be marked as obsolete, though.
On Sun, Jun 17, 2012 at
Thanks Prescott.
I noticed that we need to elect someone as Chair/VP for the project,
someone to be a representative for our collective PMC to the board. Unless
I'm mistaken, the job entails the quarterly report to the board and
communication with the board when a new PMC member is added or the
That comment is correct. We don't have support for NIOFSDirectory in .NET
(and the JVM support for it in windows has a major bug). We also don't
support MMapDirectory, because we haven't bothered to support it yet. I
think digy ported it once, but it didn't add any speed benefits, and was
on process kill.
I'll try to come up with a better way to reproduce this - hopefully Mike
will be able to suggest better ways than manual process kill...
On Thu, Jun 14, 2012 at 1:41 AM, Christopher Currens
currens.ch...@gmail.com wrote:
Mike, The codebase for lucene.net should be almost
I've gone back and forth on whether I think we're ready for graduation or
not. I had always felt like we weren't because the project isn't as active
as I'd like it to be. However, I think I've been looking at it wrong.
We've got a good enough process and we *have* made progress. If anything,
I can't guarantee that the code is 100% in compliance with java 3.0.3. All
changes that could be ported have been ported in core and most contrib
projects. There are a few things that should at least be discussed
regarding the compatibility in core:
Occur (BooleanClause) in java is converted to
[
https://issues.apache.org/jira/browse/LUCENENET-490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Currens resolved LUCENENET-490.
---
Resolution: Fixed
That is how it used to be. I believe I caused
[
https://issues.apache.org/jira/browse/LUCENENET-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13295239#comment-13295239
]
Christopher Currens commented on LUCENENET-480:
---
I'm assuming we're going
Mike, The codebase for lucene.net should be almost identical to java's
3.0.3 release, and LUCENE-1044 is included in that.
Itamar, are you committing the index regularly? I only ask because I can't
reproduce it myself by forcibly terminating the process while it's
indexing. I've tried both
[
https://issues.apache.org/jira/browse/LUCENENET-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13293189#comment-13293189
]
Christopher Currens commented on LUCENENET-493:
---
This is rather annoying
[
https://issues.apache.org/jira/browse/LUCENENET-490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Currens updated LUCENENET-490:
--
Fix Version/s: Lucene.Net 3.0.3
QueryParser is culture-sensitive
[
https://issues.apache.org/jira/browse/LUCENENET-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13286699#comment-13286699
]
Christopher Currens commented on LUCENENET-484:
---
Thanks Luc
[
https://issues.apache.org/jira/browse/LUCENENET-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Currens updated LUCENENET-484:
--
Description:
These tests will fail intermittently in Debug or Release mode
To clarify, that list is not everything missing from .NET for Metro, but
rather the types in the 637 errors I found trying to compile lucene.
On Wed, May 30, 2012 at 9:50 AM, Christopher Currens
currens.ch...@gmail.com wrote:
This MSDN page has some good information on it:
http
This MSDN page has some good information on it:
http://msdn.microsoft.com/en-us/library/windows/apps/br230302(v=vs.110).aspx,
though it's comprehensive, and not concise. This here:
http://msdn.microsoft.com/en-us/library/windows/apps/br230232(v=vs.110).aspx
is a listing of all the available
Simon,
build commit all release should work. However, we have one or two issues
with our current trunk state, as you can see. It looks like an obsolete
method was removed in IndexReader, but not all tests/projects compiled and
run before it was committed. Not a huge issue at all, since you've
I can't reproduce the failed tests in TestQueryParser.TestWildCard. Works
for me in both debug and release builds, running via R# and Gallio.
On Tue, May 29, 2012 at 10:45 AM, Prescott Nasser geobmx...@hotmail.comwrote:
my intentions to move this code into contrib, which brings the first of
Welcome, Itamar! Glad to have you aboard.
Thanks,
Christopher
On Tue, May 22, 2012 at 3:21 PM, Digy digyd...@gmail.com wrote:
Welcome Itamar!
DIGY
-Original Message-
From: Prescott Nasser [mailto:geobmx...@hotmail.com]
Sent: Wednesday, May 23, 2012 12:06 AM
To:
[
https://issues.apache.org/jira/browse/LUCENENET-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13264032#comment-13264032
]
Christopher Currens commented on LUCENENET-484:
---
Some of the tests I can
I'll take a look at it.
On Mon, Apr 23, 2012 at 1:28 PM, Prescott Nasser geobmx...@hotmail.comwrote:
If anyone is familiar with the CMS, something happened to the download
page (formatting is screwed up), but it's exactly like the other pages. I
could use another pair of eyes on it. ~P
It's in a weird place. And for the 3.0.3 version, its easiest to find the
code in the tags, rather than branches.
http://svn.apache.org/viewvc/lucene/java/tags/lucene_3_0_3/contrib/misc/src/java/org/apache/lucene/misc/
On Mon, Apr 23, 2012 at 2:20 PM, Prescott Nasser
[
https://issues.apache.org/jira/browse/LUCENENET-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Currens updated LUCENENET-485:
--
Attachment: TestFrenchAnalyzer.cs.patch
Here's a patch for tests
[
https://issues.apache.org/jira/browse/LUCENENET-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Currens updated LUCENENET-483:
--
Fix Version/s: Lucene.Net 3.0.3
Spatial Search skipping records when
it out easily.
It would also be nice if people could find bugs we could fix before
releasing it. Actually, it would be nice if people knew there was a 3.0.3
version coming out. So, I say go for it.
Thanks,
Christopher
On Thu, Apr 12, 2012 at 6:14 PM, Christopher Currens
currens.ch...@gmail.com
Core, Lucene.Net Test
Affects Versions: Lucene.Net 3.0.3
Reporter: Christopher Currens
Fix For: Lucene.Net 3.0.3
These tests will fail intermittently in Debug or Release mode, in the core test
suite:
# Lucene.Net.Index
[
https://issues.apache.org/jira/browse/LUCENENET-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Currens updated LUCENENET-484:
--
Description:
These tests will fail intermittently in Debug or Release mode
[
https://issues.apache.org/jira/browse/LUCENENET-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13249624#comment-13249624
]
Christopher Currens commented on LUCENENET-470:
---
I understand your
[
https://issues.apache.org/jira/browse/LUCENENET-481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Currens resolved LUCENENET-481.
---
Resolution: Fixed
I hope you don't mind, but I had so much free time
[
https://issues.apache.org/jira/browse/LUCENENET-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13240232#comment-13240232
]
Christopher Currens commented on LUCENENET-482:
---
The compiled binaries
[
https://issues.apache.org/jira/browse/LUCENENET-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13238661#comment-13238661
]
Christopher Currens commented on LUCENENET-481:
---
If you're talking about
: Lucene.Net
Issue Type: Task
Components: Lucene.Net Contrib, Lucene.Net Core, Lucene.Net Demo,
Lucene.Net Test
Affects Versions: Lucene.Net 2.9.4g, Lucene.Net 2.9.4, Lucene.Net 3.0.3
Reporter: Christopher Currens
We need to investigate what needs to be done
[
https://issues.apache.org/jira/browse/LUCENENET-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Currens closed LUCENENET-472.
-
Resolution: Fixed
Fix Version/s: Lucene.Net 3.0.3
Equals wasn't
[
https://issues.apache.org/jira/browse/LUCENENET-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13237204#comment-13237204
]
Christopher Currens commented on LUCENENET-463:
---
I pushed some changes
[
https://issues.apache.org/jira/browse/LUCENENET-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Currens closed LUCENENET-479.
-
Resolution: Fixed
This was fixed along with re-porting the parser
[
https://issues.apache.org/jira/browse/LUCENENET-466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Currens closed LUCENENET-466.
-
Resolution: Fixed
I've added a new stemmer in trunk called GermanDIN2Stemmer
[
https://issues.apache.org/jira/browse/LUCENENET-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Currens updated LUCENENET-476:
--
Issue Type: Bug (was: Sub-task)
Parent: (was: LUCENENET-446
Similarity is in a weird spot in the java repo:
http://svn.apache.org/viewvc/lucene/java/tags/lucene_3_0_3/contrib/queries/src/java/org/apache/lucene/search/
On Sat, Mar 3, 2012 at 1:00 PM, Prescott Nasser geobmx...@hotmail.comwrote:
Should we remove this? It looks like it's not part of the
A bit of background about what I've been doing lately on the project.
Because we've now confirmed that the .NET 3.0.3 branch is a completed port
of Java 3.0.3 version, I've been spending time trying to work on some of
the bugs and improvements that are assigned to this version. There wasn't
any
[
https://issues.apache.org/jira/browse/LUCENENET-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13211301#comment-13211301
]
Christopher Currens commented on LUCENENET-468:
---
Pretty much all classes
15, 2012 at 10:45 AM, Christopher Currens
currens.ch...@gmail.com wrote:
Erg. Was it related to the whole documentation thing? I'm pretty sure
it's frowned upon for our documentation to break SVN every time we do a
release, so we should probably figure out a solution for that. :P
it wouldn't bomb ASF's infrastructure.
I agree with Prescott that long term, using SVN for this is just not
gonna work out. Docs do change quickly.
-T
On Wed, Feb 15, 2012 at 11:18 AM, Christopher Currens
currens.ch...@gmail.com wrote:
That's similar to a suggestion Stefan made in another
into trunk? There are only a few
issues regarding .NET-ification that I think are blocking a 3.0.3 release.
Thanks,
Christopher
On Sun, Feb 5, 2012 at 11:46 AM, Christopher Currens
currens.ch...@gmail.com wrote:
2653, 2055, 2776, 2732, 2688, 2616, 2524, 2398, 2284, 2278, 2277, and 2249
I can only guarantee that these 31 bugs here (in the 3.0.3 version):
https://svn.apache.org/repos/asf/lucene/java/tags/lucene_3_0_3/CHANGES.txt are
part of the code. I mean, it's possible that other's are, but we'd really
need to check the others listed there to be sure that they are also
as
part of that changeset. I'm basing that on the fact that the last time
these bugs were updated was Dec 1st 2010, which was before the code was
released. However, we should still check to make sure.
Thanks,
Christopher
On Sun, Feb 5, 2012 at 11:37 AM, Christopher Currens
currens.ch...@gmail.com
The source that this port was done from was the java release package.
If you go to the mirrors:
http://www.apache.org/dyn/closer.cgi/lucene/java/ you'll see that they
have a 3.0.3 folder with a downloadable source zip. There are
additional thoughts I wrote down while working on it here:
I think CLS compatibility, in terms of types, is less important than
naming. CLS compliance all while keeping the index format seems like
a pretty big challenge for us to do at this point. I had worked *very
little* on CLS compliance, it was mostly fixing TopDocs and some other
small name
[
https://issues.apache.org/jira/browse/LUCENENET-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Currens updated LUCENENET-446:
--
Fix Version/s: Lucene.Net 3.0.3
Make Lucene.Net CLS Compliant
[
https://issues.apache.org/jira/browse/LUCENENET-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Currens updated LUCENENET-439:
--
Fix Version/s: Lucene.Net 3.0.3
Correctly Rethrow exceptions in C
[
https://issues.apache.org/jira/browse/LUCENENET-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13191896#comment-13191896
]
Christopher Currens commented on LUCENENET-372:
---
All of this code has
[
https://issues.apache.org/jira/browse/LUCENENET-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13191897#comment-13191897
]
Christopher Currens commented on LUCENENET-463:
---
This is, at least, on my
[
https://issues.apache.org/jira/browse/LUCENENET-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Currens updated LUCENENET-463:
--
Fix Version/s: Lucene.Net 3.0.3
Would like to be able to use
[
https://issues.apache.org/jira/browse/LUCENENET-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Currens updated LUCENENET-436:
--
Fix Version/s: Lucene.Net 3.0.3
This is a nice to have for the 3.x release
[
https://issues.apache.org/jira/browse/LUCENENET-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Currens updated LUCENENET-423:
--
Fix Version/s: Lucene.Net 3.0.3
Summary: QueryParser differences
[
https://issues.apache.org/jira/browse/LUCENENET-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Currens updated LUCENENET-179:
--
Fix Version/s: Lucene.Net 3.0.3
I haven't looked at the code, but I'm
Contrib, Lucene.Net Core
Affects Versions: Lucene.Net 2.9.4, Lucene.Net 2.9.2, Lucene.Net 3.0.3,
Lucene.Net 2.9.4g
Environment: all
Reporter: Christopher Currens
Fix For: Lucene.Net 3.0.3
Although we haven't abandoned the line-by-line port of Java lucene
Components: Lucene.Net Contrib, Lucene.Net Core, Lucene.Net Demo,
Lucene.Net Test
Affects Versions: Lucene.Net 2.9.4, Lucene.Net 2.9.2, Lucene.Net 3.0.3,
Lucene.Net 2.9.4g
Environment: all
Reporter: Christopher Currens
Fix For: Lucene.Net 3.0.3
Components: Lucene.Net Contrib, Lucene.Net Core
Affects Versions: Lucene.Net 2.9.4, Lucene.Net 3.0.3, Lucene.Net 2.9.4g
Environment: all
Reporter: Christopher Currens
Fix For: Lucene.Net 3.0.3
The Iterator pattern in Java is equivalent to IEnumerable in .NET
[
https://issues.apache.org/jira/browse/LUCENENET-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Currens updated LUCENENET-468:
--
Description:
Implement the dispose pattern as [suggested
here|http
Components: Lucene.Net Contrib, Lucene.Net Core
Affects Versions: Lucene.Net 2.9.4, Lucene.Net 3.0.3, Lucene.Net 2.9.4g
Environment: all
Reporter: Christopher Currens
Fix For: Lucene.Net 3.0.3
We should use .NET properties where ever possible. There are many
They are artifacts from java-doc. Package is for package specific comments
and overview is filled with comments about multiple packages. We can
remove them, we don't have any need for them.
Thanks,
Christopher
On Mon, Jan 23, 2012 at 11:07 PM, Prescott Nasser geobmx...@hotmail.comwrote:
All,
I just wanted to confirm everyone's stance on the coding guidelines
listed in the wiki.
https://cwiki.apache.org/confluence/display/LUCENENET/Coding+Guidelines
Are these the official guidelines we are using? If they are, has
anyone who has Resharper already created rules so others don't
[
https://issues.apache.org/jira/browse/LUCENENET-465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13191975#comment-13191975
]
Christopher Currens commented on LUCENENET-465:
---
It looks by the issue
[
https://issues.apache.org/jira/browse/LUCENENET-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13190345#comment-13190345
]
Christopher Currens commented on LUCENENET-54:
--
This affected DanishStemmer
1 - 100 of 136 matches
Mail list logo
