Hi,
Maven 2 provides a well defined and excellent build process. If the code
basis is organized according to the Maven default project layout Maven can
do amazing things without almost no configuration.
The documentation is improved and there is a free PDF document available:
http://www.merger
I like what Paul said here. I was thinking the same about "unmaintained"
contribs.
Otis
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Simpy -- http://www.simpy.com/ - Tag - Search - Share
- Original Message
From: Paul Elschot <[EMAIL PROTECTED]>
To: java-dev@lucen
[
https://issues.apache.org/jira/browse/LUCENE-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496776
]
Otis Gospodnetic commented on LUCENE-883:
-
Do you need reader=null?
Do you need to close reader explicitly he
[
https://issues.apache.org/jira/browse/LUCENE-883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Naber updated LUCENE-883:
Attachment: lucene-spellchecker-2.diff
patch to make test case work again
> make spell checker tes
make spell checker test case work again
---
Key: LUCENE-883
URL: https://issues.apache.org/jira/browse/LUCENE-883
Project: Lucene - Java
Issue Type: Bug
Affects Versions: 2.1
Reporter: Dani
[
https://issues.apache.org/jira/browse/LUCENE-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Naber updated LUCENE-882:
Attachment: lucene-spellchecker.diff
don't store but only index ngrams
> Spellchecker doesn't need
Spellchecker doesn't need to store ngrams
-
Key: LUCENE-882
URL: https://issues.apache.org/jira/browse/LUCENE-882
Project: Lucene - Java
Issue Type: Improvement
Components: Other
Affects
Thanks a lot. Sorry for the wrong list usage.
Stefano
On 5/17/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
: thanks a lot. I see part of the email was more for the users list.
: However, assuming this is not what I want (I do not want to be able to
: reconstruct a document or a good approxim
: thanks a lot. I see part of the email was more for the users list.
: However, assuming this is not what I want (I do not want to be able to
: reconstruct a document or a good approximation of it), would it be
: very disruptive for Lucene architecture avoid to store the positions?
: Would it be a
[
https://issues.apache.org/jira/browse/LUCENE-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496655
]
Yonik Seeley commented on LUCENE-881:
-
> escape() should escape the two chars | and & as well, no?
Agree.
> Que
: In fact I would rename current target "test" to "test-core"
: and make a new target "test" which depends on both "test-core"
: and "test-contrib". That way during developing you can run
: "test-core" - that should be quicker. But the nightly and the
i'm certianly on board with that ... i would
I'm not certain, but would parts of your goal be achieved by the work i've
seen floating arround Jira to refactor th MergePolicy so that it can be
handled by multiple thrads? ... if MergePolicies are refactored into their
own class with ways of indicating when/if/how a merge should be done, then
p
Grant Ingersoll <[EMAIL PROTECTED]> wrote on 17/05/2007 04:09:59:
> +1 on running the contrib tests. +1 for a policy that tests should
> be run when building a release.
>
+1 for both as well.
In fact I would rename current target "test" to "test-core"
and make a new target "test" which depends
[
https://issues.apache.org/jira/browse/LUCENE-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496634
]
Michael Busch commented on LUCENE-881:
--
You are right Yonik, || is reserved.
The QueryParser itself works corre
[
https://issues.apache.org/jira/browse/LUCENE-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496618
]
Yonik Seeley commented on LUCENE-881:
-
Sorry, I don't quite understand the problem. Could someone provide an act
[
https://issues.apache.org/jira/browse/LUCENE-881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Busch updated LUCENE-881:
-
Priority: Trivial (was: Major)
> QueryParser escaping/parsin issue with strings starting/ending
[
https://issues.apache.org/jira/browse/LUCENE-881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Busch reassigned LUCENE-881:
Assignee: Michael Busch
> QueryParser escaping/parsin issue with strings starting/ending wi
[
https://issues.apache.org/jira/browse/LUCENE-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496610
]
Michael Busch commented on LUCENE-881:
--
The problem here is that QueryParser.escape() does not escape | and &. T
Hi,
if you run Lucene as a service you want to be able to shut it down in a
certain period of time (usually 1-2 mins). This can be a problem if the
IndexWriter is in the middle of a merge when the service shutdown
request is received.
Therefore it would be nice if we had a method in IndexWri
[
https://issues.apache.org/jira/browse/LUCENE-880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Busch resolved LUCENE-880.
--
Resolution: Fixed
Lucene Fields: [New, Patch Available] (was: [Patch Available, New])
C
QueryParser escaping/parsin issue with strings starting/ending with ||
--
Key: LUCENE-881
URL: https://issues.apache.org/jira/browse/LUCENE-881
Project: Lucene - Java
Issue
+1 on running the contrib tests. +1 for a policy that tests should
be run when building a release.
On May 17, 2007, at 3:10 AM, Chris Hostetter wrote:
: Yeah, I hate to admit it and start another round of Maven vs. ANT,
Yeah, i guess i hsould have been more clear ... my question was not
Hi Daniel,
thanks a lot. I see part of the email was more for the users list.
However, assuming this is not what I want (I do not want to be able to
reconstruct a document or a good approximation of it), would it be
very disruptive for Lucene architecture avoid to store the positions?
Would it be
On Thursday 17 May 2007 00:58, Stefano Fornari wrote:
> I have a question to which I could not answer reading the
> documentation and searching the mailing list archive:
This actually belongs more to the user list... try Luke and click on the
"Reconstruct & Edit" button, then on the "Tokenized"
On Thursday 17 May 2007 09:10, Chris Hostetter wrote:
...
> It could be argued that contribs are not important enough for contrib test
> failures to result in a nightly build failing (I have no strong opinion
> about this). It could also be argued that while it's good to run test
> against the "co
: Yeah, I hate to admit it and start another round of Maven vs. ANT,
Yeah, i guess i hsould have been more clear ... my question was not about
how we could improve the build system to ensure this happens ... my
question was about wether or not this behavior is desirable/intentional
It could be a
26 matches
Mail list logo
