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 Summary: Ant should use other compilers when Sun's Javac can not be found Product: Ant Version: 1.7Alpha (nightly) Platform: Other OS/Version: other Status: NEW Severity: enhancement Priority: P2 Component: Core tasks AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Hi all, Ant gives an error message out of the box when its javac task is used, no build.compiler is set and the runtime environment doesn't have a com.sun Javac entry point. That leads to people using such runtime enviroments patching build.xml files, setting build.compiler in patched Ant shell scripts, and even writing their own com.sun Javac wrappers (java-gcj-wrapper) and setting build.compiler to a known good value in the VM itself (me in Kaffe a few days ago to make Tomcat4's pristine tarball work unpatched on Kaffe from CVS head. The JSPs didn't compile because of no Javac being found by Ant). Before I propose a solution, is there some specific way of dealing with this that's 'blessed' by Ant developers, beside 'Run Sun!' ? ;) Otherwise, I'd suggest a 'test for Javac and jikes and gcj and kjc and an external javac in java.home' before you abort' approach. cheers, dalibor topic -- 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]
