I'm getting this with 3.2:
javacc-check:
BUILD FAILED
file:D:/applications/lucene-1.3-final/build.xml:97:
##################################################################
JavaCC not found.
JavaCC Home: /applications/javacc-3.2/bin
JavaCC JAR: D:\applications\javacc-3.2\bin\bin\lib\javacc.jar
Please download and install JavaCC from:
<http://javacc.dev.java.net>
Then, create a build.properties file either in your home
directory, or within the Lucene directory and set the javacc.home
property to the path where JavaCC is installed. For example,
if you installed JavaCC in /usr/local/java/javacc-3.2, then set the
javacc.home property to:
javacc.home=/usr/local/java/javacc-3.2
If you get an error like the one below, then you have not installed
things correctly. Please check all your paths and try again.
java.lang.NoClassDefFoundError: org.javacc.parser.Main
##################################################################
even though I put a build.properties file in my root lucene directory with this in it:
javacc.home=/applications/javacc-3.2/bin
hmm?
-----Original Message-----
From: Otis Gospodnetic [mailto:[EMAIL PROTECTED]
Sent: Wed 3/24/2004 8:29 AM
To: Lucene Users List
Cc:
Subject: RE: Query syntax on Keyword field question
JavaCC 3.2 works for me.
Otis
--- Chad Small <[EMAIL PROTECTED]> wrote:
> thanks. I was in the process of getting javacc3.2 setup. I'll have
> to hunt for 2.x.
>
> chad.
>
> -----Original Message-----
> From: Morus Walter [mailto:[EMAIL PROTECTED]
> Sent: Wed 3/24/2004 8:00 AM
> To: Lucene Users List
> Cc:
> Subject: RE: Query syntax on Keyword field question
>
>
>
> Hi Chad,
>
> > But I assume this fix won't come out for some time. Is there a
> way I can get this fix sooner?
> > I'm up against a deadline and would very much like this
> functionality.
>
> Just get lucenes sources, change the line and recompile.
> The difficult part is to get a copy of JavaCC 2 (3 won't do), but I
> think
> this can be found in the archives.
>
> >
> > And to go one more step with the KeywordAnalyzer that I wrote,
> changing this method to skip the escape:
> > protected boolean isTokenChar(char c)
> > {
> > if (c == '\\')
> > {
> > return false;
> > }
> > else
> > {
> > return true;
> > }
> > }
> > The test then returns with a space:
> > healthecare.domain.lucenesearch.KeywordAnalyzer:
> > [HW-NCI_TOPICS]
> > query.ToString = +category:"HW -NCI_TOPICS" +space
> > junit.framework.ComparisonFailure: HW-NCI_TOPICS kept as-is
> > Expected:+category:HW\-NCI_TOPICS +space
> > Actual :+category:"HW -NCI_TOPICS" +space <----note space where
> escape was.
>
> Sure. If \ isn't a token char, it end's the token.
> So you will have to look for a different way of implementing the
> analyzer. Shouldn't be that difficult since you have only one token.
>
> Maybe it should be the job of the query parser to remove the escape
> character
> (would make more sense to me at least) but that would be another
> change
> of the query parser...
>
> Morus
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
> >
---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
