ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Loughran <>
Subject Re: Javac for big Projects with many errors
Date Thu, 17 Apr 2003 16:07:26 GMT

I concur; if you get errors of the time, you arent in control of your 
build. The hard part is going from where you are now, to where you want 
to be, usually in a timescale that is implausible unless conventional 
thinking regarding the unidirectionality of time is in fact horribly 
wrong :)

1. try setting up some continuous integration server like CruiseControl, 
  to alert the world whenever code or tests fail after a check in.

2. use patterns/filesets to divide up your source into sections and 
compile them in fragments

3. fix the bugs! There are no 'unimportant' errors. Maybe in the short 
term, but never in the long term.

4. add more tests. If your code doesnt even compile, I suspect the test 
process is going to be even less reliable.


Antoine Levy-Lambert wrote:
> I would see two solutions :
> - split in your ant build file the compilation of the sources which never
> have errors from the compilation of the other ones, by creating different
> targets where you use <javac> against different filesets.
> - use the try task from ant-contrib
> The best - in the long term - would be to clean up all your codebase. If you
> have a lot of source code that does not compile, you should get your
> developers to fix it, or discuss whether it can be removed.
> Hope it helps.
> Antoine
> ----- Original Message -----
> From: "Bansemir, Carsten" <>
> To: <>
> Sent: Thursday, April 17, 2003 2:39 PM
> Subject: Javac for big Projects with many errors
> Hi,
> My Problem is that I want to compile one big project (>2000 classes) using
> ant, but there are always parts of the projects wich have errors (this can
> be up to 1000 errors in different classes) but the core of the project is
> still running with that errors.
> But when I want to use Ant, then it will not run through the hole compile
> process, due to the (mostly unimportant) errors.
> I read in the mailing list that I could exclude the classes with errors, but
> is there also a way, to do this dynamically, so that I don't have to check
> if there are new errors, and that the buildfile itself checks for errors,
> and ignores them ?
> Thx, Carsten

View raw message