[jira] [Commented] (LUCENE-3242) Rename Lucene common-build.xml project name

[ https://issues.apache.org/jira/browse/LUCENE-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13054820#comment-13054820 ] Uwe Schindler commented on LUCENE-3242: --- Do it, no complaints :-) Rename Lucene

[jira] [Commented] (LUCENE-3239) drop java 5 support

[ https://issues.apache.org/jira/browse/LUCENE-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13054827#comment-13054827 ] Simon Willnauer commented on LUCENE-3239: - bq. So let me make sure we are on the

[jira] [Issue Comment Edited] (LUCENE-3239) drop java 5 support

[ https://issues.apache.org/jira/browse/LUCENE-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13054827#comment-13054827 ] Simon Willnauer edited comment on LUCENE-3239 at 6/25/11 7:07 AM:

[jira] [Updated] (LUCENE-3229) Overlaped SpanNearQuery

[ https://issues.apache.org/jira/browse/LUCENE-3229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ludovic Boutros updated LUCENE-3229: Priority: Major (was: Minor) Overlaped SpanNearQuery ---

[jira] [Updated] (LUCENE-3229) SpanNearQuery: ordered spans should not overlap

[ https://issues.apache.org/jira/browse/LUCENE-3229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Elschot updated LUCENE-3229: - Fix Version/s: 3.4 Summary: SpanNearQuery: ordered spans should not overlap (was:

[jira] [Commented] (SOLR-2619) two sfields in geospatial search

[ https://issues.apache.org/jira/browse/SOLR-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13054849#comment-13054849 ] jose rodriguez commented on SOLR-2619: -- Hi David , q={!geofilt

[JENKINS-MAVEN] Lucene-Solr-Maven-3.x #162: POMs out of sync

Build: https://builds.apache.org/job/Lucene-Solr-Maven-3.x/162/ 1 tests failed. FAILED: org.apache.lucene.index.TestCheckIndex.testLuceneConstantVersion Error Message: Invalid version: 3.3-SNAPSHOT Stack Trace: java.lang.AssertionError: Invalid version: 3.3-SNAPSHOT at

[jira] [Commented] (LUCENE-1742) Wrap SegmentInfos in public class

[ https://issues.apache.org/jira/browse/LUCENE-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13054868#comment-13054868 ] Tyheem Backer commented on LUCENE-1742: --- [Thanks|http://rullymisar.com/] Wrap

[jira] [Commented] (LUCENE-3239) drop java 5 support

[ https://issues.apache.org/jira/browse/LUCENE-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13054896#comment-13054896 ] Dawid Weiss commented on LUCENE-3239: - +1 from me. drop java 5 support

[JENKINS-MAVEN] Lucene-Solr-Maven-trunk #159: POMs out of sync

Build: https://builds.apache.org/job/Lucene-Solr-Maven-trunk/159/ No tests ran. Build Log (for compile errors): [...truncated 9467 lines...] - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands,

[jira] [Updated] (LUCENE-3234) Provide limit on phrase analysis in FastVectorHighlighter

[ https://issues.apache.org/jira/browse/LUCENE-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Sokolov updated LUCENE-3234: - Attachment: LUCENE-3234.patch Sure - the test is fragile. It was just meant to illustrate the

[jira] [Commented] (LUCENE-1889) FastVectorHighlighter: support for additional queries

[ https://issues.apache.org/jira/browse/LUCENE-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13054923#comment-13054923 ] Mike Sokolov commented on LUCENE-1889: -- I made an incremental change to FVH to

[jira] [Commented] (SOLR-2242) Get distinct count of names for a facet field

[ https://issues.apache.org/jira/browse/SOLR-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13054931#comment-13054931 ] Bill Bell commented on SOLR-2242: - re: whitespace What are the settings supposed to be for

[jira] [Commented] (SOLR-2242) Get distinct count of names for a facet field

[ https://issues.apache.org/jira/browse/SOLR-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13054932#comment-13054932 ] Bill Bell commented on SOLR-2242: - Just so you know I have been using the original patch in

[jira] [Created] (SOLR-2622) ZkSolrResourceLoader does not support getConfigDir()

ZkSolrResourceLoader does not support getConfigDir() Key: SOLR-2622 URL: https://issues.apache.org/jira/browse/SOLR-2622 Project: Solr Issue Type: Bug Components: SolrCloud, web

RE: [JENKINS-MAVEN] Lucene-Solr-Maven-3.x #162: POMs out of sync

Jenkins configs updated to set correct version number - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de -Original Message- From: Apache Jenkins Server [mailto:jenk...@builds.apache.org] Sent: Saturday, June 25, 2011 1:42 PM To:

[jira] [Commented] (LUCENE-3234) Provide limit on phrase analysis in FastVectorHighlighter

[ https://issues.apache.org/jira/browse/LUCENE-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13054935#comment-13054935 ] Digy commented on LUCENE-3234: -- I am not sure how much it is related to this issue but there

[jira] [Updated] (LUCENE-3220) Implement various ranking models as Similarities

[ https://issues.apache.org/jira/browse/LUCENE-3220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Mark Nemeskey updated LUCENE-3220: Attachment: LUCENE-3220.patch Implementation of the DFR framework added. Lots of

RE: [JENKINS-MAVEN] Lucene-Solr-Maven-trunk #159: POMs out of sync

The new common module's POM had artifactId lucene-common instead of lucene-common-module, so generate-maven-artifacts failed to find the built jar when deploying. I've committed a fix to the POM, generate-maven-artifacts succeeds for me locally. Steve -Original Message- From:

[JENKINS] Lucene-Solr-tests-only-trunk - Build # 9074 - Failure

Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/9074/ 1 tests failed. REGRESSION: org.apache.solr.cloud.CloudStateUpdateTest.testCoreRegistration Error Message: expected:2 but was:3 Stack Trace: junit.framework.AssertionFailedError: expected:2 but was:3 at

[jira] [Commented] (LUCENE-1889) FastVectorHighlighter: support for additional queries

[ https://issues.apache.org/jira/browse/LUCENE-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13054984#comment-13054984 ] Koji Sekiguchi commented on LUCENE-1889: Sounds great! bq. This doesn't take you

[jira] [Commented] (LUCENE-1889) FastVectorHighlighter: support for additional queries

[ https://issues.apache.org/jira/browse/LUCENE-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13054985#comment-13054985 ] Mike Sokolov commented on LUCENE-1889: -- No, no range queries, sorry. I don't think

[jira] [Updated] (LUCENE-1889) FastVectorHighlighter: support for additional queries

[ https://issues.apache.org/jira/browse/LUCENE-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Sokolov updated LUCENE-1889: - Attachment: LUCENE-1889.patch Patch includes FVH support for Wildcard-, Regexp- and

Re: [JENKINS-MAVEN] Lucene-Solr-Maven-trunk #159: POMs out of sync

Cheers Steve On Sun, Jun 26, 2011 at 7:44 AM, Steven A Rowe sar...@syr.edu wrote: The new common module's POM had artifactId lucene-common instead of lucene-common-module, so generate-maven-artifacts failed to find the built jar when deploying. I've committed a fix to the POM,

[JENKINS] Lucene-3.x - Build # 419 - Failure

Build: https://builds.apache.org/job/Lucene-3.x/419/ 1 tests failed. REGRESSION: org.apache.lucene.index.TestNRTThreads.testNRTThreads Error Message: Some threads threw uncaught exceptions! Stack Trace: junit.framework.AssertionFailedError: Some threads threw uncaught exceptions! at