On Feb 15, 2007, at 8:10 AM, DM Smith wrote:
I don't think that one should ever expect to build from a binary
package. Even if one could.
Here's the hitch... the demo code that comes with Lucene, as sad as
it is :(, gets shipped as source code in the binary distribution.
This makes sense. What I've just seen is that we distribute
build.xml but not common-build.xml and thus the build doesn't work,
but even copying common-build.xml to that directory the build still
fails as its trying to build Lucene itself without source code. We
need a custom build.xml for the demo code, I think. I can whip
something like that up, but it'll take me a week or so to squeeze it
in. I don't think we should hold up a release for this issue - I
suspect we shipped Lucene 2.0 like this as well.
On the positive side, the source distribution works fine (from trunk):
~/dev/lucene/dist/src/lucene-2.2-dev erik$ ant
Buildfile: build.xml
javacc-uptodate-check:
javacc-notice:
init:
clover.setup:
clover.info:
[echo]
[echo] Clover not found. Code coverage reports disabled.
[echo]
clover:
common.compile-core:
[mkdir] Created dir: /Users/erik/dev/lucene/dist/src/lucene-2.2-
dev/build/classes/java
[javac] Compiling 204 source files to /Users/erik/dev/lucene/
dist/src/lucene-2.2-dev/build/classes/java
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
compile-core:
[rmic] RMI Compiling 1 class to /Users/erik/dev/lucene/dist/src/
lucene-2.2-dev/build/classes/java
jar-core:
[jar] Building jar: /Users/erik/dev/lucene/dist/src/lucene-2.2-
dev/build/lucene-core-2.2-dev.jar
default:
BUILD SUCCESSFUL
Total time: 5 seconds
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
