Thanks Slava!
Mike
Slava Imeshev wrote:
Michael,
Here are the details of the environment:
Operating system name: Linux
Operating system architecture: i386
Operating system version: 2.4.22-10mdkenterprise
Java Runtime Environment version: 1.4.2_13
Java Runtime Environment vendo
+1
I think readability/visibility of the CHANGES, both in CHANGES.txt
and also in release announcements, news items, is important for
"enticing" people to upgrade...
Mike
Doron Cohen wrote:
As it is becoming hard to browse/navigate CHANGES.txt, how about
maintaining
it in a simple HTM
Michael,
I think you should include that list in the news item on the web
site, like we did for 2.2?
Mike
Michael Busch wrote:
Hi Team,
I added your item to the list, Grant, and announced the release
officially on java-user, java-dev, announce, and freshmeat. I also
added
a news item
I included the list on the lucene.apache.org/java site and put just a
shorter news item on the lucene.apache.org site. I just tried to keep it
shorter, because e. g. the Solr & Nutch release news items are very
short there too.
You want me to add the list on lucene.apache.org too?
-Michael
Micha
Ahh, woops, I missed that. OK, I think it's fine to leave it brief
on the main site, and then enumerate the full list on the Lucene java
site. Thanks!
Mike
On Jan 25, 2008, at 3:40 AM, Michael Busch wrote:
I included the list on the lucene.apache.org/java site and put just a
shorter ne
[
https://issues.apache.org/jira/browse/LUCENE-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-1147.
Resolution: Fixed
I just committed this.
> add option to CheckIndex to only check
[
https://issues.apache.org/jira/browse/LUCENE-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-705.
---
Resolution: Fixed
I just committed this.
> CompoundFileWriter should pre-set its fil
The token types of the standard tokenizer is not accessible
---
Key: LUCENE-1150
URL: https://issues.apache.org/jira/browse/LUCENE-1150
Project: Lucene - Java
Issue Type: Bug
[
https://issues.apache.org/jira/browse/LUCENE-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562424#action_12562424
]
Nicolas Lalevée commented on LUCENE-1150:
-
here is my workaround until it is fixed
[
https://issues.apache.org/jira/browse/LUCENE-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-1084.
Resolution: Fixed
Fix Version/s: (was: 3.0)
2.4
L
Fix StandardAnalyzer to not mis-identify HOST as ACRONYM by default
---
Key: LUCENE-1151
URL: https://issues.apache.org/jira/browse/LUCENE-1151
Project: Lucene - Java
Issue Type
I'll check it, thanks Michael.
On Jan 25, 2008 3:03 AM, Michael Busch <[EMAIL PROTECTED]> wrote:
> Forrest has a plugin called projectInfo that can generate a list of
> changes and an RSS feed from a status.xml file:
>
>
> http://forrest.apache.org/pluginDocs/plugins_0_80/org.apache.forrest.plugi
[
https://issues.apache.org/jira/browse/LUCENE-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-1120.
Resolution: Fixed
Fix Version/s: 2.4
I just committed this. Note that this
Slava,
One more question: how many CPU and CPU cores does the machine have?
Mike
On Jan 24, 2008, at 6:19 PM, Slava Imeshev wrote:
Michael,
Here are the details of the environment:
Operating system name: Linux
Operating system architecture: i386
Operating system version: 2.4.22-10m
Doron Cohen wrote:
As it is becoming hard to browse/navigate CHANGES.txt, how about maintaining
it in a simple HTML file?
Requirements are:
- fancier formatting where adequate.
- collapse/expand by release/subject
- easy to maintain...
Here is an example, containing the current (new) trunk and
SpellChecker does not work properly on calling indexDictionary after clearIndex
---
Key: LUCENE-1152
URL: https://issues.apache.org/jira/browse/LUCENE-1152
Project: Lucene - J
[
https://issues.apache.org/jira/browse/LUCENE-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reassigned LUCENE-1150:
--
Assignee: Michael McCandless
> The token types of the standard tokenizer is no
[
https://issues.apache.org/jira/browse/LUCENE-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562472#action_12562472
]
Michael McCandless commented on LUCENE-1150:
Ugh, I missed that we lost this w
Wikipedia Document Generation Changes
-
Key: LUCENE-1156
URL: https://issues.apache.org/jira/browse/LUCENE-1156
Project: Lucene - Java
Issue Type: Bug
Components: contrib/benchmark, contrib/wikip
On Jan 25, 2008 1:28 PM, Doron Cohen <[EMAIL PROTECTED]> wrote:
> I'll check it, thanks Michael.
>
> On Jan 25, 2008 3:03 AM, Michael Busch <[EMAIL PROTECTED]> wrote:
>
> > Forrest has a plugin called projectInfo that can generate a list of
> > changes and an RSS feed from a status.xml file:
> >
>
: - Need to define all developers/committers in front and assign each an ID,
: and use this ID when referring to them. I guess we can ignore this practice
...
: Person2). And BTW, AFAICT for now it does not support that P1 via P2 concept
: (though that can be requested as a new feature).
On 01/25/2008 at 2:05 PM, Chris Hostetter wrote:
> > As it is becoming hard to browse/navigate CHANGES.txt, how about
> > maintaining it in a simple HTML file?
>
> personally, i'm a fan of simple, plain text files for the
> CHANGES.txt ... easy to edit, easy to read.
I don't know about easy to re
On Jan 26, 2008 2:28 AM, Doron Cohen <[EMAIL PROTECTED]> wrote:
> and with a very long file the ability to fold sections is missing
>
Actually the pdf version gives folding and so easier navigation.
[
https://issues.apache.org/jira/browse/LUCENE-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562765#action_12562765
]
Andrzej Bialecki commented on LUCENE-997:
--
I believe this version of the patch wo
On Jan 25, 2008 9:05 PM, Chris Hostetter <[EMAIL PROTECTED]> wrote:
>
> : As it is becoming hard to browse/navigate CHANGES.txt, how about
> maintaining
> : it in a simple HTML file?
>
> personally, i'm a fan of simple, plain text files for the CHANGES.txt ...
> easy to edit, easy to read.
I agr
Well, contrib/Wikipedia has a dependency on it, but at least it is
self contained. I would love to see the Wikipedia stuff extracted out
of benchmark and be in contrib/wikipedia (thus flipping the
dependency), but the effort isn't particularly high on my list.
But I do agree, benchmark doe
[
https://issues.apache.org/jira/browse/LUCENE-1156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562674#action_12562674
]
Grant Ingersoll commented on LUCENE-1156:
-
I should amend the Template item. They
On Jan 25, 2008 8:04 PM, Grant Ingersoll <[EMAIL PROTECTED]> wrote:
> One more thought on back compatibility:
>
> Do we have the same requirements for any and all contrib modules? I
> am especially thinking about the benchmark contrib, but it probably
> applies to others as well.
>
> -Grant
>
In
[
https://issues.apache.org/jira/browse/LUCENE-997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Timm updated LUCENE-997:
-
Attachment: TimerThreadTest.java
The TimerThreadTest illustrates the accuracy of the TimerThread under lo
[
https://issues.apache.org/jira/browse/LUCENE-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll resolved LUCENE-1153.
-
Resolution: Fixed
Lucene Fields: (was: [New])
Committed revision 615329.
> Luc
[
https://issues.apache.org/jira/browse/LUCENE-997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Timm updated LUCENE-997:
-
Attachment: timeout.patch
Updated bad patch with good copy.
Created a patch using Timo's HitCollectorTim
[
https://issues.apache.org/jira/browse/LUCENE-997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Timm updated LUCENE-997:
-
Attachment: (was: timeout.patch)
> Add search timeout support to Lucene
> ---
[
https://issues.apache.org/jira/browse/LUCENE-997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Timm updated LUCENE-997:
-
Attachment: timeout.patch
Created a patch using Timo's HitCollectorTimeoutDecorator. This patch just has
[
https://issues.apache.org/jira/browse/LUCENE-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1150:
---
Attachment: LUCENE-1150.take2.patch
New patch attached, that also exposes the token
: As it is becoming hard to browse/navigate CHANGES.txt, how about maintaining
: it in a simple HTML file?
personally, i'm a fan of simple, plain text files for the CHANGES.txt ...
easy to edit, easy to read.
that said: if people want to start using a more structured changelog file
(xml/html/w
[
https://issues.apache.org/jira/browse/LUCENE-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562513#action_12562513
]
Grant Ingersoll commented on LUCENE-1153:
-
I will commit later today.
> Lucene ne
[
https://issues.apache.org/jira/browse/LUCENE-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Naveen Belkale updated LUCENE-1152:
---
Priority: Minor (was: Major)
Lucene Fields: [New, Patch Available] (was: [Patch Av
[
https://issues.apache.org/jira/browse/LUCENE-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562497#action_12562497
]
Grant Ingersoll commented on LUCENE-1155:
-
I think I am missing something here. I
System Reqs page should be release specific
---
Key: LUCENE-1154
URL: https://issues.apache.org/jira/browse/LUCENE-1154
Project: Lucene - Java
Issue Type: Bug
Components: Website
Lucene needs to ship the JUnit jar for testing
--
Key: LUCENE-1153
URL: https://issues.apache.org/jira/browse/LUCENE-1153
Project: Lucene - Java
Issue Type: Bug
Reporter: Grant Ingersol
[
https://issues.apache.org/jira/browse/LUCENE-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Naveen Belkale updated LUCENE-1152:
---
Attachment: spellchecker.diff
Suggested patch.
> SpellChecker does not work properly on cal
[
https://issues.apache.org/jira/browse/LUCENE-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1150:
---
Attachment: LUCENE-1150.patch
Attached patch fixing this. I just added a new Consta
[
https://issues.apache.org/jira/browse/LUCENE-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562485#action_12562485
]
belkale edited comment on LUCENE-1152 at 1/25/08 5:07 AM:
-
[
https://issues.apache.org/jira/browse/LUCENE-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562485#action_12562485
]
Naveen Belkale commented on LUCENE-1152:
One more small query. We have requirement
[
https://issues.apache.org/jira/browse/LUCENE-997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Timm updated LUCENE-997:
-
Attachment: LuceneTimeoutTest.java
Updated to work with latest patch.
> Add search timeout support to Lu
[
https://issues.apache.org/jira/browse/LUCENE-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562491#action_12562491
]
Grant Ingersoll commented on LUCENE-1150:
-
Why not just add them on to the Standar
BoostingTermQuery#defaultTermBoost
--
Key: LUCENE-1155
URL: https://issues.apache.org/jira/browse/LUCENE-1155
Project: Lucene - Java
Issue Type: Improvement
Components: Search
Reporter: K
[
https://issues.apache.org/jira/browse/LUCENE-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wettin updated LUCENE-1155:
Description:
This patch allows a null payload to mean something different than 1f.
(I have this
[
https://issues.apache.org/jira/browse/LUCENE-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated LUCENE-1153:
Attachment: LUCENE-1153.patch
Patch. Requires junit-3.8.2.jar in lib directory (which is
One more thought on back compatibility:
Do we have the same requirements for any and all contrib modules? I
am especially thinking about the benchmark contrib, but it probably
applies to others as well.
-Grant
On Jan 24, 2008, at 8:42 AM, Grant Ingersoll wrote:
On Jan 24, 2008, at 4:2
[
https://issues.apache.org/jira/browse/LUCENE-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562525#action_12562525
]
Michael McCandless commented on LUCENE-1150:
Good! I'll take that approach, a
[
https://issues.apache.org/jira/browse/LUCENE-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562514#action_12562514
]
Karl Wettin commented on LUCENE-1155:
-
{quote}
I think I am missing something here. If
52 matches
Mail list logo
