The Build Extensions Debugging Attributes are common to all Build Extensions Ant tasks that extend the AbstractExtensionsTask or the AbstractExtensionsTeamTask.
The following table describes the Build Extensions Debugging Attributes:
| Attribute | Description | Required |
| debugOn |
Specify true to enable Build Extensions debug facilities. The default is false. The debugOn attribute must be enabled for any debugging messages to be generated. If debugOn is enabled, at least one of the fatal, error, warn, info, flow, debug, trace, or items attributes should be enabled.
|
No |
| fatal |
Specify true to enable Build Extensions fatal messages. The default is false.
|
No |
| error |
Specify true to enable Build Extensions error messages. The default is false.
|
No |
| warn |
Specify true to enable Build Extensions warn messages. The default is false.
|
No |
| info |
Specify true to enable Build Extensions info messages. The default is false.
|
No |
| flow |
Specify true to enable Build Extensions flow (verbose) messages. The default is false. Flow messages provide basic debugging information. This is the first level of debug data.
|
No |
| debug |
Specify true to enable Build Extensions debug messages. The default is false. Debug messages provide additional debugging information. This is the second level of debug data. Enabling this attribute enables all lower debugging levels: fatal, error, warn, info, and flow.
|
No |
| trace |
Specify true to enable Build Extensions trace messages. The default is false. Trace messages provide extended debugging information. This is the third level of debug data. Enabling this attribute enables all lower debugging levels: fatal, error, warn, info, flow, and debug.
|
No |
| items |
Specify true to enable Build Extensions items messages. The default is false. Items messages provide detailed debugging information. This is the highest level of debug data. Not all tasks provide items level messages. Enabling this attribute enables all lower debugging levels: fatal, error, warn, info, flow, debug, and trace.
|
No |
| multi |
Specify true to include a thread ID in all debugging messages. The default is false. This option is especially useful in multi-processing environments where debug messages from different threads may be interleaved.
|
No |
| timer |
Specify true to include a time stamp in all debugging messages. The default is false. This option is useful when tracking timings or delays, as well as, merging debug data from different systems or platforms.
|
No |
The Build Extensions debug facilities can also be controlled by creating Ant properties and setting them to the desired value:
| Property: | Description: |
| debugOn |
Enables the Build Extensions debug facilities when set to true.
|
| fatal |
Enables fatal messages when set to true.
|
| error |
Enables error, and all lower level, messages when set to true.
|
| warn |
Enables warn, and all lower level, messages when set to true.
|
| info |
Enables info, and all lower level, messages when set to true.
|
| flow |
Enables flow, and all lower level, messages when set to true.
|
| debug |
Enables debug, and all lower level, messages when set to true.
|
| trace |
Enables trace, and all lower level, messages when set to true.
|
| items |
Enables items, and all lower level, messages when set to true.
|
| multi |
Enables thread ID inclusion in all debugging messages when set to true.
|
| timer |
Enables time stamp inclusion in all debugging messages when set to true.
|
The Build Extensions debug facilities can also be controlled by creating these Ant properties and setting them to the desired value:
The Build Extensions debug facilities can also be controlled by creating these environment properties and setting them to the desired value:
The Build Extensions debug facilities can also be controlled by creating these JVM properties and setting them to the desired value: