Developer's guide to driving the AJDT build process
The AJDT automated build process generates various artifacts not created by running an eclipse build, and now provides additional functionality such as packing JARs with the pack200 command, to produce a faster udpate site. However, getting the build working on your own machine has various gotchas, which this page hopes to help you through.
This guide assumes taht your starting point is that you have followed all the steps in the standard developer's guide here:
The first thing that is different from working with and building the source in Eclipse is the need for additional projects from CVS. Check the following out from CVS: