Eliminating Build Errors for Ant

OK, so I didn't really detail the extent pain it took to get Ant built from source in Eclipse. It essentially took downloading the source (either from SVN or the source download page) and importing it into eclipse. There are a number of ways to accomplish this. The next stage was to see how many errors you get when you try and compile. LOTS. So there are a ton of errors that essentially are similar to errors you get when using a class that you have no import statement for. In this case, there were all the import statements but Eclipse couldn't 'find' the class files. OK, so off to the Ant manual. In the installation instructions there is a dependency table with a list of libraries and their uses within Ant. Just about all of them were necessary. So I had to download the jar and then link to it in my Eclipse project. 15 libraries later, we're at 0 errors and open for business. Could their be another way? Well I have heard that Maven supposedly solves this problem but I Don't think Maven and Ant like each other too well so maybe that's the reason its awkward.
Sam

can I please find a bug ?

ok so with an ant built from source the only thing let to take the next step is find a bug. I've been on this problem for a couple of weeks. I suppose I just need to pick one and start working on it but for some reason I'm convinced that will lead to weeks of confusion.

ant releases

It never occurred to me how 'low-tech' coordinating for a new release would be. The vote consists of people responding to the corresponding email thread with their comments and a [ ] or [ X ] denoting voting nay or aye respectively. Just thought it was interesting, though I'm not sure if there is a better way. There is no real infrastructure to the ant project. There is a wiki, some source repositories, and the bug database. So it does appear that the majority (if not all) coordination must be occurring on the developers mailing list. Of course that is what ant says, I just didn't actually think it worked like that. Now on to trying to find a bug to fix...