Return-Path: Delivered-To: apmail-lucene-java-dev-archive@www.apache.org Received: (qmail 90688 invoked from network); 28 Nov 2006 19:22:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 Nov 2006 19:22:37 -0000 Received: (qmail 78216 invoked by uid 500); 28 Nov 2006 19:22:44 -0000 Delivered-To: apmail-lucene-java-dev-archive@lucene.apache.org Received: (qmail 78171 invoked by uid 500); 28 Nov 2006 19:22:43 -0000 Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-dev@lucene.apache.org Delivered-To: mailing list java-dev@lucene.apache.org Received: (qmail 78160 invoked by uid 99); 28 Nov 2006 19:22:43 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Nov 2006 11:22:43 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [128.230.18.29] (HELO mailer.syr.edu) (128.230.18.29) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Nov 2006 11:22:30 -0800 Received: from [128.230.84.138] (syru84-138.syr.edu) by mailer.syr.edu (LSMTP for Windows NT v1.1b) with SMTP id <0.15B659D4@mailer.syr.edu>; Tue, 28 Nov 2006 14:22:09 -0500 Message-ID: <456C8C61.40400@syr.edu> Date: Tue, 28 Nov 2006 14:22:09 -0500 From: Steven Rowe User-Agent: Mail/News 1.5.0.4-GroupWise-IMAP-fix (Windows/20060619) MIME-Version: 1.0 To: java-dev@lucene.apache.org Subject: Re: I want to develop an analyzer based on StandardAnalyzer References: <20061125100659.64590.qmail@web25410.mail.ukl.yahoo.com> In-Reply-To: <20061125100659.64590.qmail@web25410.mail.ukl.yahoo.com> X-Enigmail-Version: 0.94.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hello Cristophe, christophe leroy wrote: > I need an Analyzer which doesn't separate the > underscored words and with the StandardAnalyzer > functionnalities. > So, the solution is to create a new Analyzer . > > I have seen several mails about that. I tried to apply > the proposed solutions but I have a problem. [...] > C:\Documents and > Settings\CLEROY\Bureau\pb_lucene2\lucene-1.4.3-src\lucene-1.4.3 > \src\java\org\apache\lucene\analysis\standard>"C:\Documents > and Settings\CLEROY\ > Bureau\pb_lucene2\javacc-4.0\javacc-4.0\bin\javacc" > StandardTokenizer.jj [...] I don't know if your problem is being caused by this (though I suspect it is -- see below), but the standard way to rebuild the JavaCC-based parsers is via an ant target -- from Lucene's BUILD.txt: - After JavaCC is installed, create a build.properties file [...] and add the line javacc.home=/javacc where this points to the root directory of your javacc installation (the directory that contains bin/lib/javacc.jar). - To rebuild any of the JavaCC-based parsers, run "ant javacc". So, your build.properties should contain (all on one line): javacc.home = C:/Documents and Settings/CLEROY/Bureau/pb_lucene2/javacc-4.0/javacc-4.0 ---- The "javacc" ant target calls the "javacc-StandardAnalyzer" target, which generates the source files in a temporary directory, then copies them back where they need to be for compilation, in the process getting rid of ParseException.java: Good luck, Steve --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org For additional commands, e-mail: java-dev-help@lucene.apache.org