Jesse Glick wrote: > Has anyone given thought to when we drop support for running Ant on > JDK 1.2/1.3? These releases are pretty old by now and AFAIK all major > platforms have had a decent 1.4 port for a while. I am guessing most > Java developers would be using a relatively recent JDK anyway - and > those who are still using 1.2/1.3 probably don't expect to be able to > use the latest releases of every tool like Ant, either. > > Continuing to support 1.2 and 1.3 means we need to continue to have > various hacks in the codebase - long if/else clauses, reflection - > which could otherwise be removed. It means more codepaths, thus harder > code to read and more of a testing burden. It also means we cannot > easily use JDK 1.4+ APIs, and cannot use assertions at all. > > Cross-development could continue to be supported (if desired) with the > existing 'bootclasspath' and 'executable' attributes on various tasks, > which AFAIK is now complete with 'executable' added to <javadoc>. > > Granted I am probably biased as a Sun employee, since JDK 1.2 & 1.3 > are officially at "end of life". But note that you can't even run the > last JDK 1.2 maintenance release on a recent Linux distribution, > unless you use an obscure LD_PRELOAD hack (*).
agree that JDK 1.2 should not be supported > Opinions? Just testing the waters here, nothing urgent. i think a first step would be doing a quick impact analysis across core/optional task library....... --Jim Fuller --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
