You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@lucene.apache.org by Ian Lea <ia...@blackwell.co.uk> on 2002/02/08 14:01:50 UTC
Lucene Build Instructions
Today I built lucene-1.2-rc3 from the source distribution
for the first time. On the whole it was easy enough but
a couple of points:
BUILD.txt says "Install JDK 1.3". Might it be better to say
"Install JDK 1.3 or later"?. Lots of people are probably
running 1.4 already.
BUILD.txt makes no mention of javaCC. You find out soon
enough when run ant, but would be better to have it
mentioned up front. Also I couldn't get the .ant.properties
method mentioned in build.xml to work (probably finger
trouble) but copying javaCC.zip to the lucene-1.2-rc3-src/lib/
directory worked fine.
Also, by default the code as compiled from source and as
distributed in the binary download doesn't have line numbers
in stack trace dumps. This may be deliberate in which case
fine, but the line numbers do help in tracking down
problems.
--
Ian.
ian.lea@blackwell.co.uk
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Lucene Build Instructions
Posted by John David Garza <jm...@cornell.edu>.
I agree...
I also installed 1.2-rc3 from source recently (new computer). And ran
into the same problems.
One other suggestion I might add is adding a default task to the build.xml
that prints your options.
For example, in the source distribution for log4j, when doing
$ ant
in the dir where the build.xml file is located, you get a general usage
message showing all the available tasks and a short description of each.
John David Garza
jmg19@cornell.edu
On Fri, 8 Feb 2002, Ian Lea wrote:
> Today I built lucene-1.2-rc3 from the source distribution
> for the first time. On the whole it was easy enough but
> a couple of points:
>
>
> BUILD.txt says "Install JDK 1.3". Might it be better to say
> "Install JDK 1.3 or later"?. Lots of people are probably
> running 1.4 already.
>
> BUILD.txt makes no mention of javaCC. You find out soon
> enough when run ant, but would be better to have it
> mentioned up front. Also I couldn't get the .ant.properties
> method mentioned in build.xml to work (probably finger
> trouble) but copying javaCC.zip to the lucene-1.2-rc3-src/lib/
> directory worked fine.
>
>
>
> Also, by default the code as compiled from source and as
> distributed in the binary download doesn't have line numbers
> in stack trace dumps. This may be deliberate in which case
> fine, but the line numbers do help in tracking down
> problems.
>
>
>
> --
> Ian.
> ian.lea@blackwell.co.uk
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [PATCH] Re: Lucene Build Instructions
Posted by Erik Hatcher <li...@ehatchersolutions.com>.
Oops.... I see this patch went to lucene-users, but I'm sure all the -dev
folks are here too.
I would also recommend commenting out all the properties in
build.properties.sample so that if someone renames it that they'd have to
manually uncomment items to specify them - this would just make it that much
more explicit.
Erik
----- Original Message -----
From: "Erik Hatcher" <li...@ehatchersolutions.com>
To: "Lucene Users List" <lu...@jakarta.apache.org>
Sent: Friday, February 15, 2002 11:27 PM
Subject: [PATCH] Re: Lucene Build Instructions
> Ok, here's the patch. It includes my earlier patch with the "docweb"
> additions (see my previous patch for the related code). All I really did
> was paste in build.properties.
>
> So here are the steps to incorporate this:
>
> - Apply this patch
> - Rename build.properties -> build.properties.sample
>
> I did rename one property: build.war.name -> build.demo.war.name so that
the
> docweb WAR that gets built uses build.docweb.war.name.
>
> Let me know if there are any problems/questions - this patch is
> straightforward and won't cause any problems except to note the other
> changes I made with the property name change.
>
> Erik
>
>
>
> ----- Original Message -----
> From: "Daniel Calvo" <dc...@ig.com.br>
> To: "Lucene Users List" <lu...@jakarta.apache.org>
> Sent: Friday, February 15, 2002 11:54 PM
> Subject: RE: Lucene Build Instructions
>
>
> > I agree. I think this should be fixed before the official release (I've
> had trouble building Lucene and I've seen messages from
> > other users with the same problem). Can you make the changes and submit
> the patches? Then, if everybody agrees, they can be
> > commited.
> >
> > --Daniel
> >
> > > -----Original Message-----
> > > From: Erik Hatcher [mailto:lists@ehatchersolutions.com]
> > > Sent: sábado, 16 de fevereiro de 2002 00:38
> > > To: Lucene Users List
> > > Subject: Re: Lucene Build Instructions
> > >
> > >
> > > I would go so far as to even recommend that javacc.home be defined in
> > > build.xml with a default location that is the recommend "home" for it
> and if
> > > it needs adjusting it would happen via build.properties or -D
> command-line
> > > switch.
> > >
> > > Again, I'm here to help and volunteer my Ant expertise to lucene-dev.
> Just
> > > e-mail me and ask!
> > >
> > > Erik
> > >
> > >
> > > ----- Original Message -----
> > > From: "Daniel Calvo" <dc...@task.com.br>
> > > To: "Lucene Users List" <lu...@jakarta.apache.org>
> > > Sent: Friday, February 15, 2002 11:09 PM
> > > Subject: RE: Lucene Build Instructions
> > >
> > >
> > > > Hi,
> > > >
> > > > That's why I've suggested changes in build.xml to look for
> .ant.properties
> > > files (posted in the developers list) but after reading
> > > > acoliver and Erik replies I agreed with them. The best option would
be
> > > having all properties defined in build.xml and eliminate
> > > > build.properties. Each user would be responsible for the local
> > > configuration in a build.properties file (javacc.home would be
> > > > defined there) and a sample build.properties would be provided to
help
> > > this process.
> > > >
> > > > --Daniel> $ pwd
> > > > > /work/lucene-1.2-rc3-src
> > > > > $ cat .ant.properties
> > > > > javacc.home=/work/javacc2.1/bin/lib
> > > > > $ ls /work/javacc2.1/bin/lib/JavaCC.zip
> > > > > /work/javacc2.1/bin/lib/JavaCC.zip
> > > > > $ ant
> > > > > Buildfile: build.xml
> > > > >
> > > > > init:
> > > > >
> > > > > javacc_check:
> > > > > [echo]
> > > > >
> ##################################################################
> > > > > JavaCC not found.
> > > > > JavaCC Home: ./
> > > > > JavaCC Zip: .//lib/JavaCC.zip
> > > > >
> > > > > Please download and install JavaCC 2.0 from:
> > > > >
> > > > > <http://www.webgain.com/products/metamata/java_doc.html>
> > > > >
> > > > > Then, create a .ant.properties file either in your home
> > > > > directory, or within the Lucene directory and set the
> javacc.home
> > > > > property to the path where JavaCC.zip is located. For
example,
> > > > > if you installed JavaCC in /usr/local/java/javacc2.0, then
set
> the
> > > > > javacc.home property to:
> > > > >
> > > > > javacc.home=/usr/local/java/javacc2.0/bin/lib
> > > > >
> > > > > 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: COM/sun/labs/javacc/Main
> > > > >
> ##################################################################
> > > > >
> > > > > $ cp .ant.properties ~/
> > > > > $ ant
> > > > > [no change from above]
> > > > > $ cp /work/javacc2.1/bin/lib/JavaCC.zip lib/
> > > > > $ ant
> > > > > Buildfile: build.xml
> > > > >
> > > > > init:
> > > > >
> > > > > javacc_check:
> > > > >
> > > > > compile:
> > > > >
> > > > > jar:
> > > > >
> > > > > BUILD SUCCESSFUL
> > > > >
> > > > >
> > > > > So perhaps it wasn't finger trouble but something else.
> > > >
> > > >
> > > > --
> > > > To unsubscribe, e-mail:
> > > <ma...@jakarta.apache.org>
> > > > For additional commands, e-mail:
> > > <ma...@jakarta.apache.org>
> > > >
> > > >
> > >
> > >
> > > --
> > > To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> > > For additional commands, e-mail:
> <ma...@jakarta.apache.org>
> > >
> >
> >
> > --
> > To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> > For additional commands, e-mail:
> <ma...@jakarta.apache.org>
> >
> >
>
----------------------------------------------------------------------------
----
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [PATCH] Re: Lucene Build Instructions
Posted by Erik Hatcher <li...@ehatchersolutions.com>.
----- Original Message -----
From: "Daniel Calvo" <dc...@ig.com.br>
> Yep, that's what I was expecting to see but since you know Ant a lot
better than me I thought that maybe you'd come with something
> different ;-)
I don't really have any property setting tricks up my sleeve. It is
important to understand that properties are immutable and how overriding
them works though.
Erik
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: [PATCH] Re: Lucene Build Instructions
Posted by Daniel Calvo <dc...@ig.com.br>.
> From: Erik Hatcher [mailto:lists@ehatchersolutions.com]
> Ok, here's the patch. It includes my earlier patch with the "docweb"
> additions (see my previous patch for the related code). All I really did
> was paste in build.properties.
Yep, that's what I was expecting to see but since you know Ant a lot better than me I thought that maybe you'd come with something
different ;-)
Don't know about the others by I vote for incorporating these changes on the next release.
Thanks,
--Daniel
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
[PATCH] Re: Lucene Build Instructions
Posted by Erik Hatcher <li...@ehatchersolutions.com>.
Ok, here's the patch. It includes my earlier patch with the "docweb"
additions (see my previous patch for the related code). All I really did
was paste in build.properties.
So here are the steps to incorporate this:
- Apply this patch
- Rename build.properties -> build.properties.sample
I did rename one property: build.war.name -> build.demo.war.name so that the
docweb WAR that gets built uses build.docweb.war.name.
Let me know if there are any problems/questions - this patch is
straightforward and won't cause any problems except to note the other
changes I made with the property name change.
Erik
----- Original Message -----
From: "Daniel Calvo" <dc...@ig.com.br>
To: "Lucene Users List" <lu...@jakarta.apache.org>
Sent: Friday, February 15, 2002 11:54 PM
Subject: RE: Lucene Build Instructions
> I agree. I think this should be fixed before the official release (I've
had trouble building Lucene and I've seen messages from
> other users with the same problem). Can you make the changes and submit
the patches? Then, if everybody agrees, they can be
> commited.
>
> --Daniel
>
> > -----Original Message-----
> > From: Erik Hatcher [mailto:lists@ehatchersolutions.com]
> > Sent: s�bado, 16 de fevereiro de 2002 00:38
> > To: Lucene Users List
> > Subject: Re: Lucene Build Instructions
> >
> >
> > I would go so far as to even recommend that javacc.home be defined in
> > build.xml with a default location that is the recommend "home" for it
and if
> > it needs adjusting it would happen via build.properties or -D
command-line
> > switch.
> >
> > Again, I'm here to help and volunteer my Ant expertise to lucene-dev.
Just
> > e-mail me and ask!
> >
> > Erik
> >
> >
> > ----- Original Message -----
> > From: "Daniel Calvo" <dc...@task.com.br>
> > To: "Lucene Users List" <lu...@jakarta.apache.org>
> > Sent: Friday, February 15, 2002 11:09 PM
> > Subject: RE: Lucene Build Instructions
> >
> >
> > > Hi,
> > >
> > > That's why I've suggested changes in build.xml to look for
.ant.properties
> > files (posted in the developers list) but after reading
> > > acoliver and Erik replies I agreed with them. The best option would be
> > having all properties defined in build.xml and eliminate
> > > build.properties. Each user would be responsible for the local
> > configuration in a build.properties file (javacc.home would be
> > > defined there) and a sample build.properties would be provided to help
> > this process.
> > >
> > > --Daniel> $ pwd
> > > > /work/lucene-1.2-rc3-src
> > > > $ cat .ant.properties
> > > > javacc.home=/work/javacc2.1/bin/lib
> > > > $ ls /work/javacc2.1/bin/lib/JavaCC.zip
> > > > /work/javacc2.1/bin/lib/JavaCC.zip
> > > > $ ant
> > > > Buildfile: build.xml
> > > >
> > > > init:
> > > >
> > > > javacc_check:
> > > > [echo]
> > > >
##################################################################
> > > > JavaCC not found.
> > > > JavaCC Home: ./
> > > > JavaCC Zip: .//lib/JavaCC.zip
> > > >
> > > > Please download and install JavaCC 2.0 from:
> > > >
> > > > <http://www.webgain.com/products/metamata/java_doc.html>
> > > >
> > > > Then, create a .ant.properties file either in your home
> > > > directory, or within the Lucene directory and set the
javacc.home
> > > > property to the path where JavaCC.zip is located. For example,
> > > > if you installed JavaCC in /usr/local/java/javacc2.0, then set
the
> > > > javacc.home property to:
> > > >
> > > > javacc.home=/usr/local/java/javacc2.0/bin/lib
> > > >
> > > > 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: COM/sun/labs/javacc/Main
> > > >
##################################################################
> > > >
> > > > $ cp .ant.properties ~/
> > > > $ ant
> > > > [no change from above]
> > > > $ cp /work/javacc2.1/bin/lib/JavaCC.zip lib/
> > > > $ ant
> > > > Buildfile: build.xml
> > > >
> > > > init:
> > > >
> > > > javacc_check:
> > > >
> > > > compile:
> > > >
> > > > jar:
> > > >
> > > > BUILD SUCCESSFUL
> > > >
> > > >
> > > > So perhaps it wasn't finger trouble but something else.
> > >
> > >
> > > --
> > > To unsubscribe, e-mail:
> > <ma...@jakarta.apache.org>
> > > For additional commands, e-mail:
> > <ma...@jakarta.apache.org>
> > >
> > >
> >
> >
> > --
> > To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> > For additional commands, e-mail:
<ma...@jakarta.apache.org>
> >
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
>
RE: Lucene Build Instructions
Posted by Daniel Calvo <dc...@ig.com.br>.
I agree. I think this should be fixed before the official release (I've had trouble building Lucene and I've seen messages from
other users with the same problem). Can you make the changes and submit the patches? Then, if everybody agrees, they can be
commited.
--Daniel
> -----Original Message-----
> From: Erik Hatcher [mailto:lists@ehatchersolutions.com]
> Sent: sábado, 16 de fevereiro de 2002 00:38
> To: Lucene Users List
> Subject: Re: Lucene Build Instructions
>
>
> I would go so far as to even recommend that javacc.home be defined in
> build.xml with a default location that is the recommend "home" for it and if
> it needs adjusting it would happen via build.properties or -D command-line
> switch.
>
> Again, I'm here to help and volunteer my Ant expertise to lucene-dev. Just
> e-mail me and ask!
>
> Erik
>
>
> ----- Original Message -----
> From: "Daniel Calvo" <dc...@task.com.br>
> To: "Lucene Users List" <lu...@jakarta.apache.org>
> Sent: Friday, February 15, 2002 11:09 PM
> Subject: RE: Lucene Build Instructions
>
>
> > Hi,
> >
> > That's why I've suggested changes in build.xml to look for .ant.properties
> files (posted in the developers list) but after reading
> > acoliver and Erik replies I agreed with them. The best option would be
> having all properties defined in build.xml and eliminate
> > build.properties. Each user would be responsible for the local
> configuration in a build.properties file (javacc.home would be
> > defined there) and a sample build.properties would be provided to help
> this process.
> >
> > --Daniel> $ pwd
> > > /work/lucene-1.2-rc3-src
> > > $ cat .ant.properties
> > > javacc.home=/work/javacc2.1/bin/lib
> > > $ ls /work/javacc2.1/bin/lib/JavaCC.zip
> > > /work/javacc2.1/bin/lib/JavaCC.zip
> > > $ ant
> > > Buildfile: build.xml
> > >
> > > init:
> > >
> > > javacc_check:
> > > [echo]
> > > ##################################################################
> > > JavaCC not found.
> > > JavaCC Home: ./
> > > JavaCC Zip: .//lib/JavaCC.zip
> > >
> > > Please download and install JavaCC 2.0 from:
> > >
> > > <http://www.webgain.com/products/metamata/java_doc.html>
> > >
> > > Then, create a .ant.properties file either in your home
> > > directory, or within the Lucene directory and set the javacc.home
> > > property to the path where JavaCC.zip is located. For example,
> > > if you installed JavaCC in /usr/local/java/javacc2.0, then set the
> > > javacc.home property to:
> > >
> > > javacc.home=/usr/local/java/javacc2.0/bin/lib
> > >
> > > 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: COM/sun/labs/javacc/Main
> > > ##################################################################
> > >
> > > $ cp .ant.properties ~/
> > > $ ant
> > > [no change from above]
> > > $ cp /work/javacc2.1/bin/lib/JavaCC.zip lib/
> > > $ ant
> > > Buildfile: build.xml
> > >
> > > init:
> > >
> > > javacc_check:
> > >
> > > compile:
> > >
> > > jar:
> > >
> > > BUILD SUCCESSFUL
> > >
> > >
> > > So perhaps it wasn't finger trouble but something else.
> >
> >
> > --
> > To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> > For additional commands, e-mail:
> <ma...@jakarta.apache.org>
> >
> >
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Lucene Build Instructions
Posted by Erik Hatcher <li...@ehatchersolutions.com>.
I would go so far as to even recommend that javacc.home be defined in
build.xml with a default location that is the recommend "home" for it and if
it needs adjusting it would happen via build.properties or -D command-line
switch.
Again, I'm here to help and volunteer my Ant expertise to lucene-dev. Just
e-mail me and ask!
Erik
----- Original Message -----
From: "Daniel Calvo" <dc...@task.com.br>
To: "Lucene Users List" <lu...@jakarta.apache.org>
Sent: Friday, February 15, 2002 11:09 PM
Subject: RE: Lucene Build Instructions
> Hi,
>
> That's why I've suggested changes in build.xml to look for .ant.properties
files (posted in the developers list) but after reading
> acoliver and Erik replies I agreed with them. The best option would be
having all properties defined in build.xml and eliminate
> build.properties. Each user would be responsible for the local
configuration in a build.properties file (javacc.home would be
> defined there) and a sample build.properties would be provided to help
this process.
>
> --Daniel> $ pwd
> > /work/lucene-1.2-rc3-src
> > $ cat .ant.properties
> > javacc.home=/work/javacc2.1/bin/lib
> > $ ls /work/javacc2.1/bin/lib/JavaCC.zip
> > /work/javacc2.1/bin/lib/JavaCC.zip
> > $ ant
> > Buildfile: build.xml
> >
> > init:
> >
> > javacc_check:
> > [echo]
> > ##################################################################
> > JavaCC not found.
> > JavaCC Home: ./
> > JavaCC Zip: .//lib/JavaCC.zip
> >
> > Please download and install JavaCC 2.0 from:
> >
> > <http://www.webgain.com/products/metamata/java_doc.html>
> >
> > Then, create a .ant.properties file either in your home
> > directory, or within the Lucene directory and set the javacc.home
> > property to the path where JavaCC.zip is located. For example,
> > if you installed JavaCC in /usr/local/java/javacc2.0, then set the
> > javacc.home property to:
> >
> > javacc.home=/usr/local/java/javacc2.0/bin/lib
> >
> > 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: COM/sun/labs/javacc/Main
> > ##################################################################
> >
> > $ cp .ant.properties ~/
> > $ ant
> > [no change from above]
> > $ cp /work/javacc2.1/bin/lib/JavaCC.zip lib/
> > $ ant
> > Buildfile: build.xml
> >
> > init:
> >
> > javacc_check:
> >
> > compile:
> >
> > jar:
> >
> > BUILD SUCCESSFUL
> >
> >
> > So perhaps it wasn't finger trouble but something else.
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Lucene Build Instructions
Posted by Daniel Calvo <dc...@task.com.br>.
Hi,
That's why I've suggested changes in build.xml to look for .ant.properties files (posted in the developers list) but after reading
acoliver and Erik replies I agreed with them. The best option would be having all properties defined in build.xml and eliminate
build.properties. Each user would be responsible for the local configuration in a build.properties file (javacc.home would be
defined there) and a sample build.properties would be provided to help this process.
--Daniel> $ pwd
> /work/lucene-1.2-rc3-src
> $ cat .ant.properties
> javacc.home=/work/javacc2.1/bin/lib
> $ ls /work/javacc2.1/bin/lib/JavaCC.zip
> /work/javacc2.1/bin/lib/JavaCC.zip
> $ ant
> Buildfile: build.xml
>
> init:
>
> javacc_check:
> [echo]
> ##################################################################
> JavaCC not found.
> JavaCC Home: ./
> JavaCC Zip: .//lib/JavaCC.zip
>
> Please download and install JavaCC 2.0 from:
>
> <http://www.webgain.com/products/metamata/java_doc.html>
>
> Then, create a .ant.properties file either in your home
> directory, or within the Lucene directory and set the javacc.home
> property to the path where JavaCC.zip is located. For example,
> if you installed JavaCC in /usr/local/java/javacc2.0, then set the
> javacc.home property to:
>
> javacc.home=/usr/local/java/javacc2.0/bin/lib
>
> 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: COM/sun/labs/javacc/Main
> ##################################################################
>
> $ cp .ant.properties ~/
> $ ant
> [no change from above]
> $ cp /work/javacc2.1/bin/lib/JavaCC.zip lib/
> $ ant
> Buildfile: build.xml
>
> init:
>
> javacc_check:
>
> compile:
>
> jar:
>
> BUILD SUCCESSFUL
>
>
> So perhaps it wasn't finger trouble but something else.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Lucene Build Instructions
Posted by Ian Lea <ia...@blackwell.co.uk>.
"Steven J. Owens" wrote:
>
> Ian Lea (ian.lea@blackwell.co.uk) writes:
> > Today I built lucene-1.2-rc3 from the source distribution
> > for the first time. On the whole it was easy enough but
> > a couple of points:
> >
> > BUILD.txt says "Install JDK 1.3". Might it be better to say
> > "Install JDK 1.3 or later"?. Lots of people are probably
> > running 1.4 already.
>
> It also says:
>
> "Lucene runs with JDK 1.1 and later. However, if you're going to work
> with the development version of Lucene, we recommend you stick with
> the most current version of Java (at the time of this writing, JDK
> 1.3). Also, note that if you're working with the Lucene source,
> you'll need to use Ant (see below) and Ant requires at least JDK 1.1
> (and in the future will likely move to requiring JDK 1.2, according to
> the Ant install docs)."
True. My vote still goes the way I suggest but it is only a
very gentle suggestion and now I'll shut up about it.
> > BUILD.txt makes no mention of javaCC. You find out soon enough when
> > run ant, but would be better to have it mentioned up front.
>
> Hm, this was something that Doug specifically said to leave out
> of the readme. At the time, javaCC was included in the lucene lib
> directory.
In which case I might have built lucene without even knowing
that javaCC existed, which would have been fine. Now I need
to know!
> > Also I couldn't get the .ant.properties method mentioned in
> > build.xml to work (probably finger trouble) but copying javaCC.zip
> > to the lucene-1.2-rc3-src/lib/ directory worked fine.
>
> Can you clarify what problems you had with build.properties?
$ pwd
/work/lucene-1.2-rc3-src
$ cat .ant.properties
javacc.home=/work/javacc2.1/bin/lib
$ ls /work/javacc2.1/bin/lib/JavaCC.zip
/work/javacc2.1/bin/lib/JavaCC.zip
$ ant
Buildfile: build.xml
init:
javacc_check:
[echo]
##################################################################
JavaCC not found.
JavaCC Home: ./
JavaCC Zip: .//lib/JavaCC.zip
Please download and install JavaCC 2.0 from:
<http://www.webgain.com/products/metamata/java_doc.html>
Then, create a .ant.properties file either in your home
directory, or within the Lucene directory and set the javacc.home
property to the path where JavaCC.zip is located. For example,
if you installed JavaCC in /usr/local/java/javacc2.0, then set the
javacc.home property to:
javacc.home=/usr/local/java/javacc2.0/bin/lib
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: COM/sun/labs/javacc/Main
##################################################################
$ cp .ant.properties ~/
$ ant
[no change from above]
$ cp /work/javacc2.1/bin/lib/JavaCC.zip lib/
$ ant
Buildfile: build.xml
init:
javacc_check:
compile:
jar:
BUILD SUCCESSFUL
So perhaps it wasn't finger trouble but something else.
Still being picky about versions I didn't notice last week
that build.xml said to install JavaCC 2.0 whereas I seem to
have picked up version 2.1. Probably just grabbed the
current version. Very minor point certainly, but perhaps a
simple change now might avoid some confusion or questions
later on.
--
Ian.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Lucene Build Instructions
Posted by "Steven J. Owens" <pu...@darksleep.com>.
Ian Lea (ian.lea@blackwell.co.uk) writes:
> Today I built lucene-1.2-rc3 from the source distribution
> for the first time. On the whole it was easy enough but
> a couple of points:
>
> BUILD.txt says "Install JDK 1.3". Might it be better to say
> "Install JDK 1.3 or later"?. Lots of people are probably
> running 1.4 already.
It also says:
"Lucene runs with JDK 1.1 and later. However, if you're going to work
with the development version of Lucene, we recommend you stick with
the most current version of Java (at the time of this writing, JDK
1.3). Also, note that if you're working with the Lucene source,
you'll need to use Ant (see below) and Ant requires at least JDK 1.1
(and in the future will likely move to requiring JDK 1.2, according to
the Ant install docs)."
> BUILD.txt makes no mention of javaCC. You find out soon enough when
> run ant, but would be better to have it mentioned up front.
Hm, this was something that Doug specifically said to leave out
of the readme. At the time, javaCC was included in the lucene lib
directory.
> Also I couldn't get the .ant.properties method mentioned in
> build.xml to work (probably finger trouble) but copying javaCC.zip
> to the lucene-1.2-rc3-src/lib/ directory worked fine.
Can you clarify what problems you had with build.properties?
Steven J. Owens
puff@darksleep.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>