I've never understood this notion that it's better to go on compiling with you have errors!?!?!?!? What good does that do you? If you have an error, your Java code is broken, and you can't use that project. If you have independent pieces of functionality that can be used independently, then they should be different projects in the first place, compiled independently. And in any case, once you fix the errors, recompiling even a bunch of Java code only takes a few minutes, which can be decreased dramatically by using jikes (if it compiles your code...)
The modern compiler's behavior is perfectly fine with me. --DD -----Original Message----- From: Stefan Bodewig [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 17, 2002 6:56 AM To: [EMAIL PROTECTED] Subject: Re: Compile stops after first error.. how to avoid that? On Wed, 17 Jul 2002, <[EMAIL PROTECTED]> wrote: > The <javac> task still compiled all the remaining 49 classes. This > happens both for build.compiler=classic and build.compiler=jikes. but it will not work for modern. Stefan -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
