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 is work in progress, currently being updated from draft version on another machine - please don't attempt to follow this guide until this comment is removed :-) ***
This guide assumes, for now, that your starting point is that you have followed all the steps in the standard developer's guide here:
It is certainly a good idea to familiarise yourself with the Eclipse environment prior to attempting a command line build, but by no means essential. The first thing to do is create a root build directory, e.g.
and inside it two directories containing Eclipse installs (including AJDT) versions 3.2 and 3.3, e.g.:
NB The naming of these directories is important so use these names, unless you want to change config files (clue: you don't). Both these versions of Eclipse are required, as the build runs using 3.2 but needs 3.3 to build the latest versions of AJDT. So, the simplest thing to do is run up a couple of versions of Eclipse, install AJDT in each, then copy the file sets to your build directory.
Next you need to patch the two Eclipse installs to use the AJDT version of a file called "pdebuild-ant.jar". You'll find that target version under the two respective eclipse3x directories, e.g.:
or something silmilar, depending on the versions of the plugin you have. Replace this file with the AJDT version from:
again, allowing for the version of AJDT you have. This patching results in the AspectJ compiler being used instead of the Java one, so is important, as it saves you wasting a lot of time staring at lots of compilation errors :-)
You now need the AJDT build file for the version of AJDT that you want to build. This is not currently available in CVS, so has been added here as a separate document for now:
Save this to your root build directory. You now need to set up some environment variables.