Build Step - Eclipse Feature Build

This Build Step Dialog allows you to edit the general properties of this step, as well as the details for the Eclipse Feature Build that will be run for this step.

Field Definitions

• ID This is a read-only field that displays the ID for this Build Step which is unique throughout the system.
• Name This is the name of your build step and is displayed in the Build Editor Build Steps table, as well as in the Build History view.
• Type This is a read-only field that displays what type of Build Step this is.
• Execute On Server This field allows you to set up Remote Execution of build steps. It will default to the current server, but if you have more than one Build Server defined, you may pick from any server to choose where this Build Step will run.
• Timeout This is the amount of time (in Minutes) that this step will be allowed to run. If this Step does not complete in the given amount of time, it will be canceled and the Step will be marked as Failed.
• Execute Step in Parallel This indicates whether this Step will be Run in Parallel with the subsequent step. If so, this step will be run on a separate thread from the subsequent step.
• Stop Build if Step Fails This indicates whether a failure of this Step should halt the entire Build.
• Working Dir This is the Directory in which this Build Step will execute. You may use the value ${WORKDIR} to pick up the Build's Working Directory, or specify a different one as required.
• Create if Missing This is a flag that tells the build execution engine to create this Step Working Directory if it is missing. If the directory does not exist and this flag is not set, then this Step will fail.
• Erase Before Build This is a flag that tells the build execution engine to completely erase any files or folders that it finds inside the working directory prior to starting this Step. If this flag is not checked then any contents inside your working directory will be left as-is when the Step starts.
• Feature Name This is the name of your Eclipse feature.
• Eclipse Base Dir This is the directory where the Eclipse installation lives. We'll use this Eclipse installation to manage the build of your feature, so any dependencies should be present within this Eclipse installation.
• Generate build.xml Files Zed will handle generating all of the Ant build.xml files for you so that your feature is compiled properly. If you have customized these build.xml files, you can turn this option off so that Zed will not overwrite your files.
• Standard Targets There are several standard targets provided with the generated Ant build.xml files. Each of these is displayed here with a checkbox to let you turn these targets on or off.
  • clean This will run the build clean target for your Eclipse feature. This is a good item to have enabled, even if you have just checked-out from source control. Even if something was added to source control that shouldn't have been, the clean target ensures that you start from a consistent point in your build.
  • build.jars This is the main build command for your Eclipse Feature and if not included will probably result in a failed build.
  • build.update.jar This runs after build.jars and packages all of the Feature and Plugin jar files along with their Manifest files and extra components into jar packages suitable for deploying to an Eclipse Update Site. Include this if you intend to create an Eclipse Update Site for your Feature.
  • zip.distribution This runs after
• Custom Targets This allows you to add in any extra Ant build targets that you would like the compile to include. These will be added after the Standard Targets that are referenced.
• Update build.xml Files The generated build.xml files have some settings that we consider sub-optimal. The defaults generated for this build step will help you to adjust those settings. This will do a standard Search & Replace for all build.xml and MANIFEST.MF files within your feature project and dependent plugins.