[jira] Created: (LUCENE-884) Query Syntax page does not make it clear that wildcard searches are not allowed in Phrase Queries

Query Syntax page does not make it clear that wildcard searches are not allowed in Phrase Queries - Key: LUCENE-884 URL:

Re: Tests, Contribs, and Releases

+1 for renaming the 'test' target to 'test-core', and adding a 'test' target that depends on 'test-core' and 'test-contrib'. That's what other projects tend to do. Paul Elschot wrote: When a contrib fails and is not fixed, that might be a good reason to remove it from the distribution. With

[jira] Updated: (LUCENE-881) QueryParser escaping/parsin issue with strings starting/ending with ||

[ https://issues.apache.org/jira/browse/LUCENE-881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Busch updated LUCENE-881: - Attachment: lucene-881.patch Patch with additional unit tests. All tests pass. QueryParser

Re: Tests, Contribs, and Releases

Doug Cutting wrote: If a contrib package is failing tests or breaking the build, then we should file an issue in Jira. One potential patch is to remove the package (since incompatible changes are permitted in contrib). That can be proposed, and if no one with a binding vote objects, it can

[jira] Commented: (LUCENE-883) make spell checker test case work again

[ https://issues.apache.org/jira/browse/LUCENE-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497014 ] Daniel Naber commented on LUCENE-883: - Yes, the exist() method checks whether the reader is null and re-opens it

[jira] Closed: (LUCENE-884) Query Syntax page does not make it clear that wildcard searches are not allowed in Phrase Queries

[ https://issues.apache.org/jira/browse/LUCENE-884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Naber closed LUCENE-884. --- Resolution: Fixed Thanks, this is fixed now (website should update soon). Query Syntax page does

[jira] Created: (LUCENE-885) clean up build files so contrib tests are run more easily

clean up build files so contrib tests are run more easily - Key: LUCENE-885 URL: https://issues.apache.org/jira/browse/LUCENE-885 Project: Lucene - Java Issue Type: Improvement

[jira] Assigned: (LUCENE-885) clean up build files so contrib tests are run more easily

[ https://issues.apache.org/jira/browse/LUCENE-885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hoss Man reassigned LUCENE-885: --- Assignee: Hoss Man clean up build files so contrib tests are run more easily

[jira] Updated: (LUCENE-885) clean up build files so contrib tests are run more easily

[ https://issues.apache.org/jira/browse/LUCENE-885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hoss Man updated LUCENE-885: Attachment: LUCENE-885.patch Whileworking on this, i fixed a few general issues with the way some contribs

Re: Tests, Contribs, and Releases

: +1 for renaming the 'test' target to 'test-core', and adding a 'test' : target that depends on 'test-core' and 'test-contrib'. That's what : other projects tend to do. This proved a little tricker then i originally thought, but i've got it working (it even runs all tests on all contribs

Re: Tests, Contribs, and Releases

On Fri, 18 May 2007, Chris Hostetter wrote: : +1 for renaming the 'test' target to 'test-core', and adding a 'test' : target that depends on 'test-core' and 'test-contrib'. That's what : other projects tend to do. This proved a little tricker then i originally thought, but i've got it

Re: Tests, Contribs, and Releases

: allows the bdb contrib module to build for everyone. To run tests though, a : functioning install of Berkeley DB is required. : : If it's practical to install a live version of Berkeley DB on the Lucene build : bot machines, I'd have no objections in doing so. All I need is ssh access and Even