Return-Path: Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 47592 invoked from network); 21 Jul 2000 15:16:17 -0000 Received: from unknown (HELO postoffice.tidestone.com) (63.86.118.3) by locus.apache.org with SMTP; 21 Jul 2000 15:16:17 -0000 Received: by POSTOFFICE2 with Internet Mail Service (5.5.2650.21) id ; Fri, 21 Jul 2000 10:16:52 -0500 Message-ID: <418A664233C1D211AC4200105AC687C14F01F7@POSTOFFICE2> From: Jason Boehle To: "'ant-dev@jakarta.apache.org'" Subject: RE: Incremental Compilation and ant Date: Fri, 21 Jul 2000 10:16:51 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N > My question remains - why create a massive workaround for crappy compilers > when you already have a very very very fast compiler that does it for you. > Integrating this into javac task is just penalising the decent compiler and > hiding faults of bad compilers. I have never used jikes, but have heard from others that it is very fast, which is usually the reason people use it (plus the dependency checking thing sounds useful also). But to any of you using or thinking about using jikes, I would encourage you to peruse the jikes bug list: http://www10.software.ibm.com/developerworks/opensource/jikes/bugs In particular, check out the following bugs having to do with JPDA incompatibility: http://www10.software.ibm.com/developerworks/opensource/jikes/bugs/incoming? id=235 http://www10.software.ibm.com/developerworks/opensource/jikes/bugs/incoming? id=251 http://www10.software.ibm.com/developerworks/opensource/jikes/bugs/incoming? open=10 In my project, we are using Ant because we have been unable to find an IDE suite of tools that we are happy with. Therefore we have ended up with a stand-alone editor, Ant (a stand-alone make tool), and a stand-alone debugger. When you are talking about a stand-alone debugger, presently you are looking at JPDA debuggers. Since jikes generates code that is incompatible with JPDA, we are unable to use it! And of the three bugs listed above, no comments have been made to suggest that they are even being worked on. I haven't checked the latest jikes CVS or mailing list archives, so these problems could very well be addressed already. I am interested to hear some other stories on jikes and how it is used in your organization. Please email me directly though, as this may turn into an off-topic discussion that not everyone wants to participate in (but I could be wrong about that). Jason Boehle jboehle@tidestone.com