RE: Broken javadocs->site docs links

On 11/07/2008 at 1:35 PM, Doug Cutting wrote: > Steven A Rowe wrote: > > This would not entirely fix the issue; each version's > > javadocs should link to the same version of the site docs, > > rather than to the latest version (which is what I assume you > > mean here). > > Right. The javadocs s

[jira] Resolved: (LUCENE-1442) NOT_ANALYZED fields can double-count offsets

[ https://issues.apache.org/jira/browse/LUCENE-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-1442. Resolution: Fixed Fix Version/s: 2.9 Committed revision 712233. > NOT_ANAL

[jira] Resolved: (LUCENE-1441) KeywordTokenizer does not set start/end offset of the Token it produces

[ https://issues.apache.org/jira/browse/LUCENE-1441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-1441. Resolution: Fixed Fix Version/s: 2.9 Committed revision 712232. > KeywordT

[jira] Updated: (LUCENE-1442) NOT_ANALYZED fields can double-count offsets

[ https://issues.apache.org/jira/browse/LUCENE-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-1442: --- Attachment: LUCENE-1442.patch Attached patch. I plan to commit shortly. > NOT_ANAL

[jira] Created: (LUCENE-1442) NOT_ANALYZED fields can double-count offsets

NOT_ANALYZED fields can double-count offsets Key: LUCENE-1442 URL: https://issues.apache.org/jira/browse/LUCENE-1442 Project: Lucene - Java Issue Type: Bug Components: Index Affects

[jira] Updated: (LUCENE-1441) KeywordTokenizer does not set start/end offset of the Token it produces

[ https://issues.apache.org/jira/browse/LUCENE-1441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-1441: --- Attachment: LUCENE-1441.patch Attached patch. I plan to commit shortly. > KeywordT

[jira] Created: (LUCENE-1441) KeywordTokenizer does not set start/end offset of the Token it produces

KeywordTokenizer does not set start/end offset of the Token it produces --- Key: LUCENE-1441 URL: https://issues.apache.org/jira/browse/LUCENE-1441 Project: Lucene - Java Is

[jira] Updated: (LUCENE-1440) Add ability to run backwards-compatibility tests automatically

[ https://issues.apache.org/jira/browse/LUCENE-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Busch updated LUCENE-1440: -- Attachment: lucene-1440.patch Here's the patch. It adds the targets 'test-tag' and 'clean-tag

Re: Broken javadocs->site docs links

Steven A Rowe wrote: This would not entirely fix the issue; each version's javadocs should link to the same version of the site docs, rather than to the latest version (which is what I assume you mean here). Right. The javadocs should use a relative link to point to versioned docs. But, if

[jira] Created: (LUCENE-1440) Add ability to run backwards-compatibility tests automatically

Add ability to run backwards-compatibility tests automatically -- Key: LUCENE-1440 URL: https://issues.apache.org/jira/browse/LUCENE-1440 Project: Lucene - Java Issue Type: New Feat

[jira] Commented: (LUCENE-1422) New TokenStream API

[ https://issues.apache.org/jira/browse/LUCENE-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645836#action_12645836 ] Michael Busch commented on LUCENE-1422: --- {quote} Perhaps we could formalize this. We

[jira] Commented: (LUCENE-1439) Inconsistent API

[ https://issues.apache.org/jira/browse/LUCENE-1439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645829#action_12645829 ] Steven Rowe commented on LUCENE-1439: - Ivan, I'm sorry to hear that you don't have ti

[jira] Commented: (LUCENE-1439) Inconsistent API

[ https://issues.apache.org/jira/browse/LUCENE-1439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645826#action_12645826 ] Ivan.S commented on LUCENE-1439: I was thinking about this issue as a "request". Sadly, I

[jira] Updated: (LUCENE-1424) Change all mutli term querys so that they extend MultiTermQuery and allow for a constant score mode

[ https://issues.apache.org/jira/browse/LUCENE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller updated LUCENE-1424: Attachment: LUCENE-1424.patch > Change all mutli term querys so that they extend MultiTermQuery an

[jira] Commented: (LUCENE-1439) Inconsistent API

[ https://issues.apache.org/jira/browse/LUCENE-1439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645787#action_12645787 ] Uwe Schindler commented on LUCENE-1439: --- In my opinion, these are things that are re

[jira] Closed: (LUCENE-1439) Inconsistent API

[ https://issues.apache.org/jira/browse/LUCENE-1439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Busch closed LUCENE-1439. - Resolution: Incomplete I agree that there are several APIs that could be improved in Lucene. How

[jira] Updated: (LUCENE-1439) Inconsistent API

[ https://issues.apache.org/jira/browse/LUCENE-1439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller updated LUCENE-1439: Priority: Minor (was: Major) > Inconsistent API > - > > Key: LUC

[jira] Commented: (LUCENE-1439) Inconsistent API

[ https://issues.apache.org/jira/browse/LUCENE-1439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645778#action_12645778 ] Mark Miller commented on LUCENE-1439: - Patch coming? I'd classify as improvement rath

[jira] Created: (LUCENE-1439) Inconsistent API

Inconsistent API - Key: LUCENE-1439 URL: https://issues.apache.org/jira/browse/LUCENE-1439 Project: Lucene - Java Issue Type: Bug Affects Versions: 3.0 Environment: any Reporter: Ivan.S The API of

Re: Adding dependency to servlet-api

Mark - I've done a quick implementation here: I'm not familiar, yet, with what it takes (haven't read your contribution to LIA2 yet, bad, Erik, bad) to configure it - so any feedback you have on what might be needed beyond this is welcome: