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=18055>. 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=18055 javac task includes java rt.jar in classpath when using jvc compiler ------- Additional Comments From [EMAIL PROTECTED] 2003-03-19 22:26 ------- From http://ant.apache.org/manual/index.html: "Note: The Microsoft JVM/JDK is not adequate on its own, although the MS compiler is supported." The comment is a bit vague, but I take it to mean that running Ant with a Microsoft VM is not supported. (Correct me if I am wrong.) If this is the case, then why is does Ant have code that is only going to be used if running in a Microsoft VM? Otherwise if you do actually support running in the Microsoft VM, yes, the user should be given the choice of what to set includeJavaRuntime to. But if we are compiling with jvc from Ant running in the Sun VM, the Java runtime should never be included, as including Sun's Java runtime when compiling with Microsoft's compiler is always wrong. I would argue Ant should be smart enough to work this stuff out. Finally, (and I overlooked this in my original report), we have explicitly set includeJavaRuntime to false, but kept having problems. Having another look into org.apache.tools.ant.taskdefs.compilers.JVC reveals includeJavaRuntime is set to true if I don't specify a bootclasspath. So I can get things working by setting includeJavaRuntime to false, and include a nonsense bootclasspath so includeJavaRuntime is not set to true when running Ant using Sun's VM. I am happy to set includeJavaRuntime to false, but I believe shouldn't have to include a nonsense bootclasspath for this to work.
