[
https://issues.apache.org/jira/browse/LUCENE-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557921#action_12557921
]
Hoss Man commented on LUCENE-1126:
--
bq. this, as you point out, is a compile-time operati
: The short answer is: I wasn't done yet :-). I'll update the trunk and
: 2.3 branch soon. You can see a preview of the changes I'm going to make
: here: http://people.apache.org/~buschmi/preview/. The 2.3 release will
: then only have 2.3 specific docs.
i trust you :)
i figured it was a work in
Chris Hostetter wrote:
> : OK, I checked in the new web site into a new location outside of trunk:
> : lucene/java/site/. The nightly cron job must copy the files now from
>
> Uh ... point of clarification: these files all seem to be have been
> "svn add"ed (not "svn move"d or "svn copy"ied so th
: OK, I checked in the new web site into a new location outside of trunk:
: lucene/java/site/. The nightly cron job must copy the files now from
Uh ... point of clarification: these files all seem to be have been
"svn add"ed (not "svn move"d or "svn copy"ied so they don't have any
history prese
Grant Ingersoll wrote:
> Works for me.
>
> -Grant
>
OK, I checked in the new web site into a new location outside of trunk:
lucene/java/site/. The nightly cron job must copy the files now from
lucene/java/site/docs instead of lucene/java/trunk/docs. Which script do
I have to change, Grant? The c
Works for me.
-Grant
On Jan 10, 2008, at 8:13 PM, Michael Busch wrote:
Doug Cutting wrote:
Grant Ingersoll wrote:
I don't know, I think it is nice to have explicit links to previous
ones as well, but it is one extra click. I suspect that is the main
thing people want from previous versions
Doug Cutting wrote:
> Grant Ingersoll wrote:
>> I don't know, I think it is nice to have explicit links to previous
>> ones as well, but it is one extra click. I suspect that is the main
>> thing people want from previous versions so it is nice to not have to
>> dig deep into the Site Versions and
[
https://issues.apache.org/jira/browse/LUCENE-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Rowe updated LUCENE-1126:
Attachment: LUCENE-1126.patch
Compiled using JFlex 1.4.1, JDK 1.4.2
> Simplify StandardTokenizer
[
https://issues.apache.org/jira/browse/LUCENE-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557864#action_12557864
]
Steven Rowe commented on LUCENE-1126:
-
bq. I'm not positive, but couldn't this result
[
https://issues.apache.org/jira/browse/LUCENE-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557854#action_12557854
]
Hoss Man commented on LUCENE-1126:
--
bq. Switching to using JFlex's [:letter:] and [:digit
Grant Ingersoll wrote:
I don't know, I think it is nice to have explicit links to previous ones
as well, but it is one extra click. I suspect that is the main thing
people want from previous versions so it is nice to not have to dig deep
into the Site Versions and have it right there from the
Daniel Noll sent the message below addressed to me, and CC'd to java-dev. I
guess CC is not good enough for ASF's mailing list software, since I received
this message, but it never showed up on the mailing list. Belatedly forwarding
it to the list now. - Steve
On 01/07/2008 at 5:06 PM, Daniel
Grant Ingersoll wrote:
>
> Or, how about 2.3 and the current javadocs page? Such as:
>
> Javadocs
> - Latest Release -> points to latest official release
> - All Releases -> points to current javadocs page
>
OK sounds good. I will make the change!
-Michael
---
On Jan 10, 2008, at 5:02 PM, Michael Busch wrote:
Yeah, but I think the Javadocs site will become pretty full when we
add
2.3 links (and 2.4, 2.9, 3.0 in the future). Because we have to have
multiple links for core, demo, and contribs from 2.3 on.
We can age out older versions. We only hav
[
https://issues.apache.org/jira/browse/LUCENE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557814#action_12557814
]
Paul Elschot commented on LUCENE-584:
-
As for PrefixGenerator:
in my (up to date) trunk
Yeah, but I think the Javadocs site will become pretty full when we add
2.3 links (and 2.4, 2.9, 3.0 in the future). Because we have to have
multiple links for core, demo, and contribs from 2.3 on.
Maybe we could have two menu items for the two most recent releases in
the left navigation bar? Olde
I don't know, I think it is nice to have explicit links to previous
ones as well, but it is one extra click. I suspect that is the main
thing people want from previous versions so it is nice to not have to
dig deep into the Site Versions and have it right there from the
javadocs link.
-G
Was wondering if someone (Mark H :-) ) could fill me in on the status
of a few Highlighter related issues.
They are:
LUCENE-403
LUCENE-644
LUCENE-663
LUCENE-794
It seems like they all have something to do with better handling
phrases/spans/etc. I'm trying to clean up these issues and also
[
https://issues.apache.org/jira/browse/LUCENE-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-519.
---
Resolution: Duplicate
Dup of LUCENE-753.
> NIO FS implementation to avoid synchroniz
[
https://issues.apache.org/jira/browse/LUCENE-893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-893:
--
Component/s: (was: Store)
Search
Description:
Spinoff of LUCEN
[
https://issues.apache.org/jira/browse/LUCENE-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557800#action_12557800
]
Grant Ingersoll commented on LUCENE-644:
Is this still an issue? Does this speedup
[
https://issues.apache.org/jira/browse/LUCENE-645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll resolved LUCENE-645.
Resolution: Fixed
Last report is this is fixed.
> Highligter fails to include non-token at
Michael Busch wrote:
Hi all,
I just created the release artifacts (incl. maven artifacts) from the
2.3 branch and uploaded the files to
http://people.apache.org/~buschmi/staging_area/lucene_2_3/rc1/.
Let's try to use the next days for testing to ensure that we find
serious bugs or build proble
Hi,
currently the binary release artifacts only contain the unified javadocs
view, not the new separate ones for core, demo and contribs. This means
that some of the links in the docs don't work.
I suppose we should change this, however it increases the size of the
binaries significantly:
lucene-
Simplify StandardTokenizer JFlex grammar
Key: LUCENE-1126
URL: https://issues.apache.org/jira/browse/LUCENE-1126
Project: Lucene - Java
Issue Type: Improvement
Components: Analysis
Affec
Hi,
first of all: sorry for the late response!
I'm not sure why we need the new javadocs page? The users can access the
javadocs from old releases by using the "Site Versions" links.
Can we just keep the Javadocs menu in the left navigation bar and rename
it to "Lucene 2.3.0 API"?
Here's a prev
[
https://issues.apache.org/jira/browse/LUCENE-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll resolved LUCENE-424.
Resolution: Incomplete
Assignee: (was: Lucene Developers)
Needs unit test and, id
[
https://issues.apache.org/jira/browse/LUCENE-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557787#action_12557787
]
Grant Ingersoll commented on LUCENE-387:
Could we get a patch for this?
> Contrib:
[
https://issues.apache.org/jira/browse/LUCENE-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557787#action_12557787
]
Grant Ingersoll commented on LUCENE-387:
Could we get a patch for this?
> Contrib:
[
https://issues.apache.org/jira/browse/LUCENE-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll reassigned LUCENE-494:
--
Assignee: Grant Ingersoll
> Analyzer for preventing overload of search service by queri
[
https://issues.apache.org/jira/browse/LUCENE-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557785#action_12557785
]
Grant Ingersoll commented on LUCENE-494:
This seems generally useful and could go i
[
https://issues.apache.org/jira/browse/LUCENE-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll resolved LUCENE-321.
Resolution: Incomplete
Assignee: (was: Lucene Developers)
Needs unit tests
> [PA
Hi Daniel,
On 01/07/2008 at 5:06 PM, Daniel Noll wrote:
> I wish the tokeniser could just use Character.isLetter and
> Character.isDigit instead of having to know all the ranges itself, since
> the JRE already has all this information. Character.isLetter does
> return true for CJK characters thou
[
https://issues.apache.org/jira/browse/LUCENE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557755#action_12557755
]
Michael Busch commented on LUCENE-584:
--
{quote}
On the take3 patch of 10 Jan 2008:
{qu
[
https://issues.apache.org/jira/browse/LUCENE-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll resolved LUCENE-559.
Resolution: Incomplete
Needs unit tests and a patch would be nice.
> Turkish Analyzer for
[
https://issues.apache.org/jira/browse/LUCENE-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll resolved LUCENE-210.
Resolution: Won't Fix
Assignee: (was: Lucene Developers)
> [PATCH] Never write an
[
https://issues.apache.org/jira/browse/LUCENE-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll resolved LUCENE-677.
Resolution: Won't Fix
Can use the Snowball Italian
> Italian Analyzer
>
>
Michael McCandless wrote:
>
> OK I carried my two fixes (LUCENE-1117, LUCENE-1125) to 2.3 branch!
>
> Mike
Great! I'll build RC2 soon!
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTE
[
https://issues.apache.org/jira/browse/LUCENE-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-1125.
Resolution: Fixed
Fixed on trunk & 2.3 branch.
> Excessive Arrays.fill(0) in Docu
OK I carried my two fixes (LUCENE-1117, LUCENE-1125) to 2.3 branch!
Mike
On Jan 10, 2008, at 12:48 PM, Michael Busch wrote:
Mike,
do you want to merge this into the 2.3 branch before I build RC2?
-Michael
[EMAIL PROTECTED] wrote:
Author: mikemccand
Date: Thu Jan 10 02:12:18 2008
New Revis
OK will do.
Mike
Michael Busch wrote:
Mike,
do you want to merge this into the 2.3 branch before I build RC2?
-Michael
[EMAIL PROTECTED] wrote:
Author: mikemccand
Date: Thu Jan 10 02:12:18 2008
New Revision: 610738
URL: http://svn.apache.org/viewvc?rev=610738&view=rev
Log:
LUCENE-1117: f
[
https://issues.apache.org/jira/browse/LUCENE-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557735#action_12557735
]
Michael McCandless commented on LUCENE-1125:
{quote}
OK, why don't you commit
Mike,
do you want to merge this into the 2.3 branch before I build RC2?
-Michael
[EMAIL PROTECTED] wrote:
> Author: mikemccand
> Date: Thu Jan 10 02:12:18 2008
> New Revision: 610738
>
> URL: http://svn.apache.org/viewvc?rev=610738&view=rev
> Log:
> LUCENE-1117: fix EnwikiDocMaker to not hang w
[
https://issues.apache.org/jira/browse/LUCENE-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557723#action_12557723
]
Michael Busch commented on LUCENE-1125:
---
{quote}
The fix is very low risk. All tests
[
https://issues.apache.org/jira/browse/LUCENE-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1125:
---
Attachment: LUCENE-1125.patch
Attached patch. I ran a test where I index the first
Excessive Arrays.fill(0) in DocumentsWriter drastically slows down small docs
(3.9X slowdown!)
--
Key: LUCENE-1125
URL: https://issues.apache.org/jira/browse/LUCENE-1125
I'll try and push organizing the unit tests up in my todo list.
Also though, it would be nice to make sure Michael Goddard's patch gets
in. He has something that looks like it will add support for
ConstantScoreRangeQuery's. I am fiddling with that now.
- Mark
Otis Gospodnetic (JIRA) wrote:
[
https://issues.apache.org/jira/browse/LUCENE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557595#action_12557595
]
Paul Elschot commented on LUCENE-584:
-
On the take3 patch of 10 Jan 2008:
SortedVIntLi
[
https://issues.apache.org/jira/browse/LUCENE-1117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557586#action_12557586
]
Michael McCandless commented on LUCENE-1117:
OK I just committed the fix to NO
[
https://issues.apache.org/jira/browse/LUCENE-831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Busch reassigned LUCENE-831:
Assignee: Michael Busch
> Complete overhaul of FieldCache API/Implementation
>
Chris Hostetter wrote:
> : I just created the release artifacts (incl. maven artifacts) from the
> : 2.3 branch and uploaded the files to
> : http://people.apache.org/~buschmi/staging_area/lucene_2_3/rc1/.
>
> Some misc comments while purusing the release artifacts...
>
> 1) the release release s
[
https://issues.apache.org/jira/browse/LUCENE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Busch updated LUCENE-584:
-
Attachment: lucene-584-take3-part2.patch
lucene-584-take3-part1.patch
OK, I creat
52 matches
Mail list logo
