We haven't written detailed documentation of the new build process yet. The goals were to restore module build consistency, ease the creation of new modules (by default, we automatically build new module directories when they appear) and improve efficiency by supporting developer-defined module manifests (instead of ever-growing hard-coded module lists).

The standard.modules file should appear in your /server directory (same place as the main build.xml). If this file doesn't exist then you'll need to fix your enlistment.

You have a few options:

- Modify your local standard.modules file to include just the path to your module. A standard "ant build" will then build only your module, none of the others.
- Create an alternate .modules file (say, "cyto.modules") and invoke "ant build -DmodulesFile=cyto.modules" to build your module
- Create a build.xml file in your module directory that defines a "build_module" target. This target should invoke sub_build_module in the main build.xml (if you want your module to ever be built by the standard build), but you can define whatever other targets you want ("build", etc.). This will restore the previous behavior. The core, query, flow, wiki, et. al modules have build.xml files that you can use as a model.

Adam