Hi Otis,
I'm asking, because it looks like your compiler is not finding Reader
and IOException classes, both of which are in java.io.* package, which
I see imported in StandardTokenizer.java as 'import java.io.*;'.
In my copy of StandardTokenizer.java, there is no 'import java.io.*;'
(and in
I don't understand this. StandardTokenizer.java hasn't changed since
last year.
I have packaged Lucene such that 'ant javacc' is called at package
build time. I now see the problem - 'import java.io.*;' has been
removed from StandardTokenizer.jj in Lucene 1.4.1. When I put that
line back in,
Ok, Lucene 1.4.1 has been uploaded to Debian. Hopefully it will have
enough time to percolate before the sarge release.
Now that that is taken care of, I'm curious about the status of gcj
compilation. Packaging Lucene as a native library might be useful for
projects such as PyLucene, and it is
It's easy enough for folks to compile Lucene this way
I'm having trouble, warnings and error messages appended. This is for
Lucene 1.4.1. One of the few Debian specific changes was to call the
jarball 1.4 instead of the default 1.5-rc1-dev designation in
build.xml.
rode:~ gcj --version
gcj
Hi all,
I am the Debian package maintainer for Lucene, and I'm having build
problems with 1.4.1. We are very close to a major Debian release (code
named 'sarge'), and the window for changes is very small. Can someone
please help me in the next day or two, otherwise Debian stable will ship
Lucene
