DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23900>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23900 Compilation fails in ant, but not in command line ------- Additional Comments From [EMAIL PROTECTED] 2003-10-22 14:40 ------- You are right, your work around will work, but this is not what I want. This is a case when the javac compiler inside ant does not work as the javac compiler outside ant. What I want is to reference the source not the compiled files. The javac compiler knows how to handle this situation (when the compiler does not find a compiled class, it will search for a Java source file, using the CLASSPATH). We are using Rational (IBM) Clearcase as our version control. Clearcase has an audit feature that can trace what files are accessed during a compilation. By making sure the compilation will access only source files not compiled files, I will get a clean list of dependencies on the Java sources. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
