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=21783>. 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=21783 ANT 1.5.3 doesn't allow use of classic compiler on j2se 1.4.1_02 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Additional Comments From [EMAIL PROTECTED] 2003-07-22 18:49 ------- Ant 1.5 no longer supports the classic compiler in Java1.4. This is by design and is documented. Most critically, there was no classic compiler in Java1.4.0, only modern. The fix went in to stop people asking for classic when there wasnt one, which was breaking the Gump nightly build on java1.4. judging by your report Sun have relented and put the old entry point back in, which is nice, and almost compensates for their moving the javah entry point in Java1.4.2. Stability of entry points is an ongoing issue with the JDK. Even if Java1.4.1 has added a backwards compatible entry point, Ant is not going to try and put classic support back in as it would cause more confusion. What do we do for version 1.4.2? What about 1.4.3, when we dont know what will be in it? It is much simpler to say 'no classic in 1.4+' and be done with it, I am afraid. Try giving ant the full path to the classic compiler adapter, if you really want the classic mode: build.compiler=org.apache.tools.ant.taskdefs.compilers.Javac12 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
