DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=34138>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=34138 ------- Additional Comments From [EMAIL PROTECTED] 2005-03-24 11:48 ------- Test for JavaEnvUtils.getJDKExecutable("javac") would work, for JVMs that come with an executable named javac. But if we used that, we'd also assume that it was command line compatible with Sun's. Testing for jikes or gcj is more difficult, you'd have to code up OS specific diagnostics to know the difference between "command not found" and "compilation error". Well, we could search for the executable in PATH (the functionality is already there in ExecTask#resolveExecutable. But what should be the order of preference? Personally I'd prefer jikes over kjc, that much ist sure. Steve might even prefer jikes over Sun's javac 8-) It would be rather easy to say we use gcj if we detect we are running in libgcj. Or jvc when running in Microsoft's VM. What would be the best fit if we know Ant is running in Kaffe? -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
