The buildtools/common.xml build file provides this set of base targets:
all: Cleans, builds, and installs the current module and its sub-modules. Note that, in theStore.EStore.Versionedmodule, thealltarget is overridden to also build any Flex elements required for the Business Control Center.clean: In preparation for another build, deletes the temporary build directory with the JAR files, compiled Java classes and other temporary files that are generated by thebuildtarget. Executes for the current module and its sub-modules.build: Compiles and jars the source Java classes. Also, replaces any tokens in the configuration files and jars them. The output of this target is stored in temporary files in themodule-name/builddirectory. Executes for the current module only.install: Replaces the class and configuration JAR files in the install directory with copies of the temporary files produced during thebuildtarget execution. Executes for the current module only.updateconfig: Replaces any tokens in the configuration files, jars them and copies them to the install directory. By default,updateconfigexecutes for the current module and its sub-modules; however, this target is overridden in theStoremodule to execute for the sub-modules only. See Targets in the Store/build.xml File and Token Substitution in Configuration Files for more information.compile: Compiles and jars the Java classes for the current module only. The output of this target is stored in a temporary file in the module’sbuilddirectory. Note that this target does not get executed for sub-modules.
To make its targets available across all Commerce Reference Store modules, the common.xml build file must be imported by all modules, as described in Maintaining the Priority Order of Targets and Properties. When custom behavior is required for a module, you can override the base targets defined in common.xml by providing a new definition for the target in the module’s build.xml file.
