I'll have a look at this later today or tomorrow (don't have
source code + project handy at the moment), but somebody
else might get to it before me.
Otis
----- Original Message ----
From: Tom Hill <solr-list zvents.com>
To: solr-dev lucene.apache.org
Sent: Friday, July 27, 2007 12:43:09 AM
Subject: Re: FW: EdgeNGramTokenizer errors in eclipse
On 7/26/07, Sundling, Paul <paul.sundling sonyconnect.com> wrote:
>
> Has anyone else noticed this? I didn't get any
response on the user
> list.
Yes, I have the same problem. The ant build works.
I just deleted that file, and it compile fine.
That may cause problems when I try to enable spell checking
next week,
though.
Tom
Paul Sundling
>
> -----Original Message-----
> From: Sundling, Paul
> Sent: Tuesday, July 24, 2007 4:55 PM
> To: solr-user lucene.apache.org
> Subject: EdgeNGramTokenizer errors in eclipse
>
>
> I checked out the latest solr source code from
subversion and put it in
> an eclipse project. I used all the jars for the
project (had to add
> junit). I get errors in eclipse about two constants
not being defined
> in one of the library jars:
>
> (based on imports
org.apache.lucene.analysis.ngram.EdgeNGramTokenizer)
> EdgeNGramTokenizer.DEFAULT_MAX_GRAM_SIZE
> and
> EdgeNGramTokenizer.DEFAULT_MAX_GRAM_SIZE
>
> are not defined. So was a class changed that this Solr
class depends
> on?
>
>
>
> The error happens in
org.apache.solr.analysis.EdgeNGramTokenizerFactory:
>
> maxGramSize = (maxArg != null ?
Integer.parseInt(maxArg) :
> EdgeNGramTokenizer.DEFAULT_MAX_GRAM_SIZE);
> String minArg = args.get("minGramSize");
> minGramSize = (minArg != null ?
Integer.parseInt(minArg) :
> EdgeNGramTokenizer.DEFAULT_MIN_GRAM_SIZE);
>
>
> Am I doing something wrong?
>
> Paul Sundling
>
>
>
>
|