Thanks Mike. I realized the issue was not defined. I appreciate the guidance about process...very much.

Billy

Mike Klaas wrote:
On 2-Nov-07, at 11:02 PM, [EMAIL PROTECTED] wrote:


In a message dated 11/2/07 6:54:25 PM, [EMAIL PROTECTED] writes:


Even if
the actual problem is at the Lucene level, perhaps it would be worth
considering changes to the default to get around it.


newbie here. is this common practice? find a bug in a tightly coupled
dependency and not deal with it there?

No--we fix bugs in Lucene if there is a genuine problem there. However, it isn't clear that this is a Lucene-caused problem.

-Mike

Reply via email to