> Another reason not to like it is that compiler error messages no longer
> reference the proper source file. I'm a fan of Emacs' M-x compile command,
> which lets you jump, with C-c C-c, from a compilation error message to the
> offending line. But this is not as useful when the offending line is in a
> temporary file, where you don't want to edit it.
>
> It is possible to both have and eat one's cake here. I have set up build
> systems which put generated files (JavaCC stuff, .class files, etc.) in
> temporary directories, but leave the source files in their original
> location. It's a bit more complicated, but I'd prefer it to the present
> situation. Can you modify Lucene's build.xml to do this? Thanks.
Ant should make this quite easy to do; at worst you need two JAVAC tasks
in the compile task; maybe not even that if you set up the file paths
correctly.
BTW, for anyone who hasn't yet figured this out, if you use ant and emacs,
if you set your compile command to
(cd $LUCENE_ROOT; ant -emacs)
emacs will be able to interpret the error messages and take you to where
they occur.
_______________________________________________
Lucene-dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/lucene-dev
