Greetings, all, I've been hiding at home to minimize distractions so that I can push out the new build system as fast as possible. As of right now, I have a subset of targets (clean, junit, quickStart, freshStart, and those they depend upon) working with a subset of modules (build, kernel, installer, statistics, report, telemetry, stdext, perf, and ant).
My goal is to port enough modules by Friday for everyone to be able to move over to the new build system for their daily development activities. To get there, it would be helpful if folks would let me know what modules beyond those listed above need conversion. Please email me your requests ASAP and I'll try to get them completed by Friday, along with a minimal users guide to get you started. For the most part, the top-level interface is almost identical to what you're using now; the major user-level difference is speed. Under the hood, of course, things are completely different. So, my phase one is to get all of the active modules ported, both to relieve your pain and to get some additional usage data. My phase two is to port the inactive modules and the rest of the targets (things like javadoc, cvs*, etc.) so that we can then move the daily build system over to it. Phase three will occur when we move to Version 7 module structure and subversion, and will require folks to write their own v7.local.build.xml files. Hopefully that will be just a matter of cutting and pasting from the current ones. Phase four will be the 'auto-configure' task, which will generate the modules.build.xml file by reading in a config file from each hackystat module. Currently, modules.build.xml is hand-written, but it should be quite straightforward to automatically generate it. (It turns out that Christoph was right after all: the auto-configure task will need to implement a dependency chain algorithm, or at least hack the one already implemented in Ant. I couldn't eliminate all of the <ant> and <antcall> targets without tossing that feature of the current system.) Cheers, Philip
