Transitions

The Transitions section contains an entry for each transition defined in the build configuration. This is a critical section of the XML document as it ties together how items get built by bringing together the items defined in the sources and targets sections with the transitions that use or generate them.

XML Example 1 | XML Example 2 | Description
<TransitionScripts> | <TransitionScripts> | Opening tag for the transitions section. All transitions for this configuration are defined within the opening tag and the closing tag.
<TransitionScript Id="143"> | <TransitionScript Id="142"> | Opening tag for this particular transition that contains the unique id for it.
<Script Id="59"> | <Script Id="58"> | Opening tag for the script to be used for this transition that contains the unique id for it.
<type> 1 </type> | <type> 1 </type> | Build Script to be used for this transition. This is a defined numeric type value that indicates how the build script was entered or is being used See page 35 for more information.
<scriptName> ![CDATA[build_script_ant.bat]] </scriptName> | <scriptName> ![CDATA[build_script_ javac.bat]] </scriptName> | Build script name.
<outputIds> 128 </outputIds> | <outputIds> 126 </outputIds> | File output(s) of this transition as identified by the id. The definition of items listed here must appear in the targets section of the file. This is very important for piecing together the transitions and targets sections.
<inputSourceIds> 106 </inputSourceIds> | <inputSourceIds> 101 </inputSourceIds> | File input(s) of this transition that are true source files as identified by id. The definition of items listed here must appear in the sources section of the file. This is very important for piecing together the transitions and sources sections.
<inputTargetIds> # </inputTargetIds> |  | File input(s) of this transition that are generated from other transitions as identified by the id. The definition of items listed here must appear in the targets section of the file. This is very important for piecing together the transitions and targets sections.
<Options> ... </Options> |  | Option to be used for this transition. This is defined by id (unique to the database), option name, and option values. If the option values are related to a build tool, the relationship is also defined here.
<OptionGroupIds> # </OptionGroupIds> |  | Option Group id(s) (unique to the database) tied to this transition.
<templateId> 0 </templateId> | <templateId> 0 </templateId> | Transition Rule Template id used to create this transition.
<transitionType> 0 </transitionType> | <transitionType> 0 </transitionType> | Expand (value 1) or no-expand (value 0) the wildcard inputs for this transition.
<transitionOrder> 0 </transitionOrder> | <transitionOrder> 2 </transitionOrder> | Build order assigned to this transition.
</Script> | </Script> | Closing tag for a single script.
</TransitionScripts> | </TransitionScripts> | Closing tag for a single transition.
</TransitionScript> | </TransitionScript> | Closing tag for the transitions section.