[jira] Resolved: (LUCENENET-341) Fix "Compiler warnings to worry about"

[ https://issues.apache.org/jira/browse/LUCENENET-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Digy resolved LUCENENET-341. Resolution: Fixed Thanks Andy. All paches applied. DIGY > Fix "Compiler warnings to worry about" >

[jira] Commented: (LUCENENET-341) Fix "Compiler warnings to worry about"

[ https://issues.apache.org/jira/browse/LUCENENET-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835832#action_12835832 ] Andy Pook commented on LUCENENET-341: - Changing ISerializable ctors to private was c

[jira] Updated: (LUCENENET-341) Fix "Compiler warnings to worry about"

[ https://issues.apache.org/jira/browse/LUCENENET-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Pook updated LUCENENET-341: Attachment: LUCENENET-341-Term.patch LUCENENET-341-NumericRangeQuery.patch

[jira] Updated: (LUCENENET-341) Fix "Compiler warnings to worry about"

[ https://issues.apache.org/jira/browse/LUCENENET-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Pook updated LUCENENET-341: Attachment: LUCENENET-341-SupportClass.ThreadClass.patch Add GetHashCode method Fixes CS0661: 'S

[jira] Created: (LUCENENET-341) Fix "Compiler warnings to worry about"

Fix "Compiler warnings to worry about" -- Key: LUCENENET-341 URL: https://issues.apache.org/jira/browse/LUCENENET-341 Project: Lucene.Net Issue Type: Bug Reporter: Andy Pook Priorit

Re: Lucene + Windows 2008 R2 performance issues

Our servers are virtualized with Hyper-V, the iSCSI SAN LUN is exposed only to the host the "clients" don't know about its existence, they're just plain hard drives as far as they're concerned. If you look at the "Cached" value in Task Manager on R2, you'll see that it is not as big as the who

Re: Compiler warnings to worry about?

I'd prefer "single issue with three patches". DIGY On Fri, Feb 19, 2010 at 3:00 PM, Andy Pook wrote: > Subscribed > > 1- Ah, hadn't spotted ISerializable. However, the recommendation for > combining ISerializable and sealed classes is to use private instead > of protected. ( > http://msdn.micros

Re: using Porter

I just complied it myself. However I am still curious as to whether there is a version floating around somewhere. Pam On Fri, Feb 19, 2010 at 8:04 AM, Pamela Foxcroft wrote: > Can anyone tell me where I can get the snowball.dll from? > > There was a lucene.net.dll, but I can't find the snowball

Re: using Porter

Can anyone tell me where I can get the snowball.dll from? There was a lucene.net.dll, but I can't find the snowball one? Thanks Pam On Fri, Feb 19, 2010 at 7:50 AM, Pamela Foxcroft wrote: > Thanks Ben and Michael! > > Pam > > > On Thu, Feb 18, 2010 at 2:45 PM, Ben Martz wrote: > >> Pamela, >>

Re: Compiler warnings to worry about?

Subscribed 1- Ah, hadn't spotted ISerializable. However, the recommendation for combining ISerializable and sealed classes is to use private instead of protected. (http://msdn.microsoft.com/en-us/library/ms182343(VS.80).aspx - "For a sealed class, make the constructor private; otherwise, make it p

Re: using Porter

Thanks Ben and Michael! Pam On Thu, Feb 18, 2010 at 2:45 PM, Ben Martz wrote: > Pamela, > > I strongly recommend than anyone planning to work with Lucene.Net follows > Michael's suggestion and reads LIA for background but once you've done > that, > here's a summary in just a few lines that may