You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucenenet.apache.org by "Doug Sale (JIRA)" <ji...@apache.org> on 2008/11/25 04:14:45 UTC
[jira] Created: (LUCENENET-164) upgrade from version 2.3.1. to
2.3.2
upgrade from version 2.3.1. to 2.3.2
------------------------------------
Key: LUCENENET-164
URL: https://issues.apache.org/jira/browse/LUCENENET-164
Project: Lucene.Net
Issue Type: Improvement
Reporter: Doug Sale
This issue is a placeholder for attaching a comprehensive patch upgrading the SVN HEAD of Lucene.Net from 2.3.1 candidate to 2.3.2 candidate.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
RE: [jira] Commented: (LUCENENET-164) upgrade from version 2.3.1. to 2.3.2
Posted by Digy <di...@gmail.com>.
I am not sure about LUCENENET-173 patch. Some mono users may benefit of it but some users are getting errors while using it. Besides that it is not a complete builder for .NET applications. It doesn't handle embedded resources, conditional compilations etc. And monodevelop makes all these quite well.
DIGY.
-----Original Message-----
From: George Aroush (JIRA) [mailto:jira@apache.org]
Sent: Thursday, March 19, 2009 3:22 AM
To: lucene-net-dev@incubator.apache.org
Subject: [jira] Commented: (LUCENENET-164) upgrade from version 2.3.1. to 2.3.2
[ https://issues.apache.org/jira/browse/LUCENENET-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683271#action_12683271 ]
George Aroush commented on LUCENENET-164:
-----------------------------------------
Hi DIGY,
I have no objection. I'm 1/2 way done reviewing the patch for 2.3.2, and expect to finish it over the weekend; worse case we can make changes to the trunk after you created a 2.3.1 tag. If you need help on creating the tag, let me know.
Before you do so, please do the following in the trunk:
1) Resolve LUCENENET-173 in the current trunk (this is a good patch to have and carry over).
2) update \trunk\C#\src\HISTORY.txt and label it as "final". E.g.:
18Mar09:
- Release: Apache Lucene.Net.2.3.1 build 003 "final"
3) Check that all AssemblyInfo.cs files have the correct build number (in \trunk\C#\src\ only, this is since we didn't touch anything in contrib)
Regards,
-- George
> upgrade from version 2.3.1. to 2.3.2
> ------------------------------------
>
> Key: LUCENENET-164
> URL: https://issues.apache.org/jira/browse/LUCENENET-164
> Project: Lucene.Net
> Issue Type: Improvement
> Reporter: Doug Sale
> Attachments: 2.3.2-Candidate.patch, LUCENENET-106 Patch for v2.3.2.patch, TestIndexModifier.patch
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> This issue is a placeholder for attaching a comprehensive patch upgrading the SVN HEAD of Lucene.Net from 2.3.1 candidate to 2.3.2 candidate.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
RE: [jira] Commented: (LUCENENET-164) upgrade from version 2.3.1. to 2.3.2
Posted by George Aroush <ge...@aroush.net>.
I will take a stab at reviewing this patch soon, but non-committers can also
review and comment which is always welcome.
-- George
> -----Original Message-----
> From: Digy [mailto:digydigy@gmail.com]
> Sent: Thursday, December 18, 2008 2:51 PM
> To: lucene-net-dev@incubator.apache.org
> Subject: RE: [jira] Commented: (LUCENENET-164) upgrade from
> version 2.3.1. to 2.3.2
>
> Hi Andreas,
>
> The patches in JIRA are just proposals and are applied to
> trunk only after they are reviewed by committers. The review
> process sometimes takes a long time since it is done at spare
> time of committers.
>
> DIGY
>
>
>
> -----Original Message-----
> From: Andreas Mummenhoff [mailto:anmum@online.de]
> Sent: Thursday, December 18, 2008 9:06 PM
> To: lucene-net-dev@incubator.apache.org
> Subject: AW: [jira] Commented: (LUCENENET-164) upgrade from
> version 2.3.1.
> to 2.3.2
>
> Hello Digy,
>
> why nobody applies this patches to the current SVN trunk?
>
> People just downloading the trunk and not knowing about jira
> don't get the "best" version available? Why?
>
>
> greetings,
> Andreas
>
> > -----Ursprüngliche Nachricht-----
> > Von: Digy (JIRA) [mailto:jira@apache.org]
> > Gesendet: Donnerstag, 18. Dezember 2008 18:44
> > An: lucene-net-dev@incubator.apache.org
> > Betreff: [jira] Commented: (LUCENENET-164) upgrade from
> version 2.3.1.
> > to 2.3.2
> >
> >
> > [
> > https://issues.apache.org/jira/browse/LUCENENET-164?page=com.a
> tlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&fo
> cusedCommentId
> =12657827#action_12657827 ]
> >
> > Digy commented on LUCENENET-164:
> > --------------------------------
> >
> > I forgot to say. All Nunit tests pass.
> >
> > DIGY.
> >
> > > upgrade from version 2.3.1. to 2.3.2
> > > ------------------------------------
> > >
> > > Key: LUCENENET-164
> > > URL:
> > https://issues.apache.org/jira/browse/LUCENENET-164
> > > Project: Lucene.Net
> > > Issue Type: Improvement
> > > Reporter: Doug Sale
> > > Attachments: 2.3.2-Candidate.patch, LUCENENET-106
> Patch for
> > > v2.3.2.patch, TestIndexModifier.patch
> > >
> > > Original Estimate: 0h
> > > Remaining Estimate: 0h
> > >
> > > This issue is a placeholder for attaching a comprehensive
> > patch upgrading the SVN HEAD of Lucene.Net from 2.3.1 candidate to
> > 2.3.2 candidate.
> >
> > --
> > This message is automatically generated by JIRA.
> > -
> > You can reply to this email to add a comment to the issue online.
> >
>
RE: [jira] Commented: (LUCENENET-164) upgrade from version 2.3.1. to 2.3.2
Posted by Digy <di...@gmail.com>.
Hi Andreas,
The patches in JIRA are just proposals and are applied to trunk only after
they are reviewed by committers. The review process sometimes takes a long
time since it is done at spare time of committers.
DIGY
-----Original Message-----
From: Andreas Mummenhoff [mailto:anmum@online.de]
Sent: Thursday, December 18, 2008 9:06 PM
To: lucene-net-dev@incubator.apache.org
Subject: AW: [jira] Commented: (LUCENENET-164) upgrade from version 2.3.1.
to 2.3.2
Hello Digy,
why nobody applies this patches to the current SVN trunk?
People just downloading the trunk and not knowing about jira don't get the
"best" version available? Why?
greetings,
Andreas
> -----Ursprüngliche Nachricht-----
> Von: Digy (JIRA) [mailto:jira@apache.org]
> Gesendet: Donnerstag, 18. Dezember 2008 18:44
> An: lucene-net-dev@incubator.apache.org
> Betreff: [jira] Commented: (LUCENENET-164) upgrade from
> version 2.3.1. to 2.3.2
>
>
> [
> https://issues.apache.org/jira/browse/LUCENENET-164?page=com.a
tlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId
=12657827#action_12657827 ]
>
> Digy commented on LUCENENET-164:
> --------------------------------
>
> I forgot to say. All Nunit tests pass.
>
> DIGY.
>
> > upgrade from version 2.3.1. to 2.3.2
> > ------------------------------------
> >
> > Key: LUCENENET-164
> > URL:
> https://issues.apache.org/jira/browse/LUCENENET-164
> > Project: Lucene.Net
> > Issue Type: Improvement
> > Reporter: Doug Sale
> > Attachments: 2.3.2-Candidate.patch, LUCENENET-106 Patch for
> > v2.3.2.patch, TestIndexModifier.patch
> >
> > Original Estimate: 0h
> > Remaining Estimate: 0h
> >
> > This issue is a placeholder for attaching a comprehensive
> patch upgrading the SVN HEAD of Lucene.Net from 2.3.1
> candidate to 2.3.2 candidate.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
Re: AW: [jira] Commented: (LUCENENET-164) upgrade from version 2.3.1.
to 2.3.2
Posted by "xzxz@mail.ru" <xz...@mail.ru>.
Andreas Mummenhoff ?????:
> Hello Digy,
>
> why nobody applies this patches to the current SVN trunk?
>
> People just downloading the trunk and not knowing about jira don't get the
> "best" version available? Why?
>
+1000!
>
> greetings,
> Andreas
>
>
>> -----Ursprüngliche Nachricht-----
>> Von: Digy (JIRA) [mailto:jira@apache.org]
>> Gesendet: Donnerstag, 18. Dezember 2008 18:44
>> An: lucene-net-dev@incubator.apache.org
>> Betreff: [jira] Commented: (LUCENENET-164) upgrade from
>> version 2.3.1. to 2.3.2
>>
>>
>> [
>> https://issues.apache.org/jira/browse/LUCENENET-164?page=com.a
>>
> tlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId
> =12657827#action_12657827 ]
>
>> Digy commented on LUCENENET-164:
>> --------------------------------
>>
>> I forgot to say. All Nunit tests pass.
>>
>> DIGY.
>>
>>
>>> upgrade from version 2.3.1. to 2.3.2
>>> ------------------------------------
>>>
>>> Key: LUCENENET-164
>>> URL:
>>>
>> https://issues.apache.org/jira/browse/LUCENENET-164
>>
>>> Project: Lucene.Net
>>> Issue Type: Improvement
>>> Reporter: Doug Sale
>>> Attachments: 2.3.2-Candidate.patch, LUCENENET-106 Patch for
>>> v2.3.2.patch, TestIndexModifier.patch
>>>
>>> Original Estimate: 0h
>>> Remaining Estimate: 0h
>>>
>>> This issue is a placeholder for attaching a comprehensive
>>>
>> patch upgrading the SVN HEAD of Lucene.Net from 2.3.1
>> candidate to 2.3.2 candidate.
>>
>> --
>> This message is automatically generated by JIRA.
>> -
>> You can reply to this email to add a comment to the issue online.
>>
>>
>
>
>
AW: [jira] Commented: (LUCENENET-164) upgrade from version 2.3.1. to 2.3.2
Posted by Andreas Mummenhoff <an...@online.de>.
Hello Digy,
why nobody applies this patches to the current SVN trunk?
People just downloading the trunk and not knowing about jira don't get the
"best" version available? Why?
greetings,
Andreas
> -----Ursprüngliche Nachricht-----
> Von: Digy (JIRA) [mailto:jira@apache.org]
> Gesendet: Donnerstag, 18. Dezember 2008 18:44
> An: lucene-net-dev@incubator.apache.org
> Betreff: [jira] Commented: (LUCENENET-164) upgrade from
> version 2.3.1. to 2.3.2
>
>
> [
> https://issues.apache.org/jira/browse/LUCENENET-164?page=com.a
tlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId
=12657827#action_12657827 ]
>
> Digy commented on LUCENENET-164:
> --------------------------------
>
> I forgot to say. All Nunit tests pass.
>
> DIGY.
>
> > upgrade from version 2.3.1. to 2.3.2
> > ------------------------------------
> >
> > Key: LUCENENET-164
> > URL:
> https://issues.apache.org/jira/browse/LUCENENET-164
> > Project: Lucene.Net
> > Issue Type: Improvement
> > Reporter: Doug Sale
> > Attachments: 2.3.2-Candidate.patch, LUCENENET-106 Patch for
> > v2.3.2.patch, TestIndexModifier.patch
> >
> > Original Estimate: 0h
> > Remaining Estimate: 0h
> >
> > This issue is a placeholder for attaching a comprehensive
> patch upgrading the SVN HEAD of Lucene.Net from 2.3.1
> candidate to 2.3.2 candidate.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
RE: [jira] Commented: (LUCENENET-164) upgrade from version 2.3.1. to 2.3.2
Posted by George Aroush <ge...@aroush.net>.
I don't think so. Let me have further look at this one tonight.
-- George
> -----Original Message-----
> From: Digy [mailto:digydigy@gmail.com]
> Sent: Thursday, March 19, 2009 3:15 PM
> To: lucene-net-dev@incubator.apache.org
> Subject: RE: [jira] Commented: (LUCENENET-164) upgrade from
> version 2.3.1. to 2.3.2
>
> Hi George,
>
>
>
> >> 3) Check that all AssemblyInfo.cs files have the correct
> build number
> >> (in \trunk\C#\src\ only, this is since we didn't touch anything in
> >> contrib)
>
>
>
> Is LUCENENET-156
> (https://issues.apache.org/jira/browse/LUCENENET-156)
> resolved? Since I see a 31/Dec/08 dated patch after your last
> comment at 30/Dec/08
>
> Can we close this issue? Should we update AssemblyInfo.cs?
>
>
>
> DIGY
>
>
>
> -----Original Message-----
> From: George Aroush (JIRA) [mailto:jira@apache.org]
> Sent: Thursday, March 19, 2009 3:22 AM
> To: lucene-net-dev@incubator.apache.org
> Subject: [jira] Commented: (LUCENENET-164) upgrade from
> version 2.3.1. to 2.3.2
>
>
>
>
>
> [
> https://issues.apache.org/jira/browse/LUCENENET-164?page=com.a
tlassian.jira.plugin.system.issuetabpanels:comment->
tabpanel&focusedCommentId=12683271#action_12683271 ]
>
>
>
> George Aroush commented on LUCENENET-164:
>
> -----------------------------------------
>
>
>
> Hi DIGY,
>
>
>
> I have no objection. I'm 1/2 way done reviewing the patch
> for 2.3.2, and expect to finish it over the weekend; worse
> case we can make changes to the trunk after you created a
> 2.3.1 tag. If you need help on creating the tag, let me know.
>
>
>
> Before you do so, please do the following in the trunk:
>
>
>
> 1) Resolve LUCENENET-173 in the current trunk (this is a good
> patch to have and carry over).
>
>
>
> 2) update \trunk\C#\src\HISTORY.txt and label it as "final". E.g.:
>
>
>
> 18Mar09:
>
> - Release: Apache Lucene.Net.2.3.1 build 003 "final"
>
>
>
> 3) Check that all AssemblyInfo.cs files have the correct
> build number (in \trunk\C#\src\ only, this is since we didn't
> touch anything in contrib)
>
>
>
> Regards,
>
>
>
> -- George
>
>
>
> > upgrade from version 2.3.1. to 2.3.2
>
> > ------------------------------------
>
> >
>
> > Key: LUCENENET-164
>
> > URL:
> > https://issues.apache.org/jira/browse/LUCENENET-164
>
> > Project: Lucene.Net
>
> > Issue Type: Improvement
>
> > Reporter: Doug Sale
>
> > Attachments: 2.3.2-Candidate.patch, LUCENENET-106 Patch for
> > v2.3.2.patch, TestIndexModifier.patch
>
> >
>
> > Original Estimate: 0h
>
> > Remaining Estimate: 0h
>
> >
>
> > This issue is a placeholder for attaching a comprehensive
> patch upgrading the SVN HEAD of Lucene.Net from 2.3.1
> candidate to 2.3.2 candidate.
>
>
>
> --
>
> This message is automatically generated by JIRA.
>
> -
>
> You can reply to this email to add a comment to the issue online.
>
>
RE: [jira] Commented: (LUCENENET-164) upgrade from version 2.3.1. to 2.3.2
Posted by Digy <di...@gmail.com>.
Hi George,
>> 3) Check that all AssemblyInfo.cs files have the correct build number (in \trunk\C#\src\ only, this is since we didn't touch anything in contrib)
Is LUCENENET-156 (https://issues.apache.org/jira/browse/LUCENENET-156) resolved? Since I see a 31/Dec/08 dated patch after your last comment at 30/Dec/08
Can we close this issue? Should we update AssemblyInfo.cs?
DIGY
-----Original Message-----
From: George Aroush (JIRA) [mailto:jira@apache.org]
Sent: Thursday, March 19, 2009 3:22 AM
To: lucene-net-dev@incubator.apache.org
Subject: [jira] Commented: (LUCENENET-164) upgrade from version 2.3.1. to 2.3.2
[ https://issues.apache.org/jira/browse/LUCENENET-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683271#action_12683271 ]
George Aroush commented on LUCENENET-164:
-----------------------------------------
Hi DIGY,
I have no objection. I'm 1/2 way done reviewing the patch for 2.3.2, and expect to finish it over the weekend; worse case we can make changes to the trunk after you created a 2.3.1 tag. If you need help on creating the tag, let me know.
Before you do so, please do the following in the trunk:
1) Resolve LUCENENET-173 in the current trunk (this is a good patch to have and carry over).
2) update \trunk\C#\src\HISTORY.txt and label it as "final". E.g.:
18Mar09:
- Release: Apache Lucene.Net.2.3.1 build 003 "final"
3) Check that all AssemblyInfo.cs files have the correct build number (in \trunk\C#\src\ only, this is since we didn't touch anything in contrib)
Regards,
-- George
> upgrade from version 2.3.1. to 2.3.2
> ------------------------------------
>
> Key: LUCENENET-164
> URL: https://issues.apache.org/jira/browse/LUCENENET-164
> Project: Lucene.Net
> Issue Type: Improvement
> Reporter: Doug Sale
> Attachments: 2.3.2-Candidate.patch, LUCENENET-106 Patch for v2.3.2.patch, TestIndexModifier.patch
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> This issue is a placeholder for attaching a comprehensive patch upgrading the SVN HEAD of Lucene.Net from 2.3.1 candidate to 2.3.2 candidate.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (LUCENENET-164) upgrade from version 2.3.1. to
2.3.2
Posted by "George Aroush (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683271#action_12683271 ]
George Aroush commented on LUCENENET-164:
-----------------------------------------
Hi DIGY,
I have no objection. I'm 1/2 way done reviewing the patch for 2.3.2, and expect to finish it over the weekend; worse case we can make changes to the trunk after you created a 2.3.1 tag. If you need help on creating the tag, let me know.
Before you do so, please do the following in the trunk:
1) Resolve LUCENENET-173 in the current trunk (this is a good patch to have and carry over).
2) update \trunk\C#\src\HISTORY.txt and label it as "final". E.g.:
18Mar09:
- Release: Apache Lucene.Net.2.3.1 build 003 "final"
3) Check that all AssemblyInfo.cs files have the correct build number (in \trunk\C#\src\ only, this is since we didn't touch anything in contrib)
Regards,
-- George
> upgrade from version 2.3.1. to 2.3.2
> ------------------------------------
>
> Key: LUCENENET-164
> URL: https://issues.apache.org/jira/browse/LUCENENET-164
> Project: Lucene.Net
> Issue Type: Improvement
> Reporter: Doug Sale
> Attachments: 2.3.2-Candidate.patch, LUCENENET-106 Patch for v2.3.2.patch, TestIndexModifier.patch
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> This issue is a placeholder for attaching a comprehensive patch upgrading the SVN HEAD of Lucene.Net from 2.3.1 candidate to 2.3.2 candidate.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (LUCENENET-164) upgrade from version 2.3.1. to
2.3.2
Posted by "Digy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Digy updated LUCENENET-164:
---------------------------
Attachment: LUCENENET-106 Patch for v2.3.2.patch
I attach a patch for Lucene.Net 2.3.2 to solve the memory-leakage bug that exists since v2.1
DIGY
> upgrade from version 2.3.1. to 2.3.2
> ------------------------------------
>
> Key: LUCENENET-164
> URL: https://issues.apache.org/jira/browse/LUCENENET-164
> Project: Lucene.Net
> Issue Type: Improvement
> Reporter: Doug Sale
> Attachments: 2.3.2-Candidate.patch, LUCENENET-106 Patch for v2.3.2.patch, TestIndexModifier.patch
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> This issue is a placeholder for attaching a comprehensive patch upgrading the SVN HEAD of Lucene.Net from 2.3.1 candidate to 2.3.2 candidate.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (LUCENENET-164) upgrade from version 2.3.1. to
2.3.2
Posted by "Digy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Digy updated LUCENENET-164:
---------------------------
Attachment: TestIndexModifier.patch
TestIndexModifier.TestIndexWithThreads:
Access to static field(idStack) by multiple threads is not synchronized.
DIGY
> upgrade from version 2.3.1. to 2.3.2
> ------------------------------------
>
> Key: LUCENENET-164
> URL: https://issues.apache.org/jira/browse/LUCENENET-164
> Project: Lucene.Net
> Issue Type: Improvement
> Reporter: Doug Sale
> Attachments: 2.3.2-Candidate.patch, TestIndexModifier.patch
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> This issue is a placeholder for attaching a comprehensive patch upgrading the SVN HEAD of Lucene.Net from 2.3.1 candidate to 2.3.2 candidate.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (LUCENENET-164) upgrade from version 2.3.1. to
2.3.2
Posted by "Doug Sale (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Doug Sale updated LUCENENET-164:
--------------------------------
Attachment: 2.3.2-Candidate.patch
Comprehensive upgrade patch from Lucene.Net 2.3.1 candidate to 2.3.2 candidate.
Affects the following files:
Index: src/Lucene.Net/Analysis/Standard/StandardTokenizer.cs
Index: src/Lucene.Net/Analysis/Standard/StandardTokenizerImpl.cs
Index: src/Lucene.Net/Analysis/Standard/StandardTokenizerImpl.jflex
Index: src/Lucene.Net/Index/CheckIndex.cs
Index: src/Lucene.Net/Index/DocumentsWriter.cs
Index: src/Lucene.Net/Index/IndexModifier.cs
Index: src/Lucene.Net/Index/IndexWriter.cs
Index: src/Lucene.Net/Index/LogMergePolicy.cs
Index: src/Lucene.Net/Index/SegmentMerger.cs
Index: src/Lucene.Net/Store/BufferedIndexInput.cs
Index: src/Lucene.Net/Store/FSDirectory.cs
Index: src/Test/Analysis/TestAnalyzers.cs
Index: src/Test/Index/TestAddIndexesNoOptimize.cs
Index: src/Test/Index/TestFieldsReader.cs
Index: src/Test/Index/TestIndexWriter.cs
Index: src/Test/Util/_TestUtil.cs
> upgrade from version 2.3.1. to 2.3.2
> ------------------------------------
>
> Key: LUCENENET-164
> URL: https://issues.apache.org/jira/browse/LUCENENET-164
> Project: Lucene.Net
> Issue Type: Improvement
> Reporter: Doug Sale
> Attachments: 2.3.2-Candidate.patch
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> This issue is a placeholder for attaching a comprehensive patch upgrading the SVN HEAD of Lucene.Net from 2.3.1 candidate to 2.3.2 candidate.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (LUCENENET-164) upgrade from version 2.3.1. to
2.3.2
Posted by "Digy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683197#action_12683197 ]
Digy commented on LUCENENET-164:
--------------------------------
Hi All,
I plan to create a 2_3_1 tag (a snapshot of the current trunk) and then apply "2.3.2-Candidate.patch" to the trunk.
Any other ideas? Objections?
DIGY
> upgrade from version 2.3.1. to 2.3.2
> ------------------------------------
>
> Key: LUCENENET-164
> URL: https://issues.apache.org/jira/browse/LUCENENET-164
> Project: Lucene.Net
> Issue Type: Improvement
> Reporter: Doug Sale
> Attachments: 2.3.2-Candidate.patch, LUCENENET-106 Patch for v2.3.2.patch, TestIndexModifier.patch
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> This issue is a placeholder for attaching a comprehensive patch upgrading the SVN HEAD of Lucene.Net from 2.3.1 candidate to 2.3.2 candidate.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (LUCENENET-164) upgrade from version 2.3.1. to
2.3.2
Posted by "Digy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659364#action_12659364 ]
Digy commented on LUCENENET-164:
--------------------------------
LUCENENET-106 patch is applied to current trunk. So no need for "LUCENENET-106 Patch for v2.3.2.patch"
DIGY.
> upgrade from version 2.3.1. to 2.3.2
> ------------------------------------
>
> Key: LUCENENET-164
> URL: https://issues.apache.org/jira/browse/LUCENENET-164
> Project: Lucene.Net
> Issue Type: Improvement
> Reporter: Doug Sale
> Attachments: 2.3.2-Candidate.patch, LUCENENET-106 Patch for v2.3.2.patch, TestIndexModifier.patch
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> This issue is a placeholder for attaching a comprehensive patch upgrading the SVN HEAD of Lucene.Net from 2.3.1 candidate to 2.3.2 candidate.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (LUCENENET-164) upgrade from version 2.3.1. to
2.3.2
Posted by "Digy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688026#action_12688026 ]
Digy commented on LUCENENET-164:
--------------------------------
Hi All,
Current Lucene.Net version (2.3.1) is moved to https://svn.apache.org/repos/asf/incubator/lucene.net/tags/Lucene.Net_2_3_1/
and 2.3.2-Candidate.patch is commited to trunk.
DIGY
> upgrade from version 2.3.1. to 2.3.2
> ------------------------------------
>
> Key: LUCENENET-164
> URL: https://issues.apache.org/jira/browse/LUCENENET-164
> Project: Lucene.Net
> Issue Type: Improvement
> Reporter: Doug Sale
> Attachments: 2.3.2-Candidate.patch, LUCENENET-106 Patch for v2.3.2.patch, TestIndexModifier.patch
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> This issue is a placeholder for attaching a comprehensive patch upgrading the SVN HEAD of Lucene.Net from 2.3.1 candidate to 2.3.2 candidate.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (LUCENENET-164) upgrade from version 2.3.1. to
2.3.2
Posted by "Digy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650651#action_12650651 ]
Digy commented on LUCENENET-164:
--------------------------------
My first impression: Excellent work!
Only one test fails. TestIndexModifier.TestIndexWithThreads.
{code}
Lucene.Net.Index.TestIndexModifier.TestIndexWithThreads : An unhandled System.SystemException was thrown while
executing this test : Internal error: 2 deleted 0 documents, term=id:266
at Lucene.Net.Index.IndexThread.Run() in F:\Lucene\DotNet\2.3.2\src\Test\Index\TestIndexModifier.cs:line 328
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
{code}
I think, I got this error a few times with 2.3.1 too.
As far as I can see, LUCENENET-160 is left out in the patch. if this patch is committed, it should be reopened.
Thanks Doug.
DIGY
> upgrade from version 2.3.1. to 2.3.2
> ------------------------------------
>
> Key: LUCENENET-164
> URL: https://issues.apache.org/jira/browse/LUCENENET-164
> Project: Lucene.Net
> Issue Type: Improvement
> Reporter: Doug Sale
> Attachments: 2.3.2-Candidate.patch
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> This issue is a placeholder for attaching a comprehensive patch upgrading the SVN HEAD of Lucene.Net from 2.3.1 candidate to 2.3.2 candidate.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (LUCENENET-164) upgrade from version 2.3.1. to
2.3.2
Posted by "Digy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657827#action_12657827 ]
Digy commented on LUCENENET-164:
--------------------------------
I forgot to say. All Nunit tests pass.
DIGY.
> upgrade from version 2.3.1. to 2.3.2
> ------------------------------------
>
> Key: LUCENENET-164
> URL: https://issues.apache.org/jira/browse/LUCENENET-164
> Project: Lucene.Net
> Issue Type: Improvement
> Reporter: Doug Sale
> Attachments: 2.3.2-Candidate.patch, LUCENENET-106 Patch for v2.3.2.patch, TestIndexModifier.patch
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> This issue is a placeholder for attaching a comprehensive patch upgrading the SVN HEAD of Lucene.Net from 2.3.1 candidate to 2.3.2 candidate.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (LUCENENET-164) upgrade from version 2.3.1. to
2.3.2
Posted by "George Aroush (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683281#action_12683281 ]
George Aroush commented on LUCENENET-164:
-----------------------------------------
Hi DIGY,
One more thing. Please apply LUCENENET-168. It's a good patch.
Thanks.
-- George
> upgrade from version 2.3.1. to 2.3.2
> ------------------------------------
>
> Key: LUCENENET-164
> URL: https://issues.apache.org/jira/browse/LUCENENET-164
> Project: Lucene.Net
> Issue Type: Improvement
> Reporter: Doug Sale
> Attachments: 2.3.2-Candidate.patch, LUCENENET-106 Patch for v2.3.2.patch, TestIndexModifier.patch
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> This issue is a placeholder for attaching a comprehensive patch upgrading the SVN HEAD of Lucene.Net from 2.3.1 candidate to 2.3.2 candidate.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (LUCENENET-164) upgrade from version 2.3.1. to 2.3.2
Posted by "Digy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Digy closed LUCENENET-164.
--------------------------
Resolution: Fixed
Thanks Doug!
> upgrade from version 2.3.1. to 2.3.2
> ------------------------------------
>
> Key: LUCENENET-164
> URL: https://issues.apache.org/jira/browse/LUCENENET-164
> Project: Lucene.Net
> Issue Type: Improvement
> Reporter: Doug Sale
> Attachments: 2.3.2-Candidate.patch, LUCENENET-106 Patch for v2.3.2.patch, TestIndexModifier.patch
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> This issue is a placeholder for attaching a comprehensive patch upgrading the SVN HEAD of Lucene.Net from 2.3.1 candidate to 2.3.2 candidate.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.