| << definitions << | Table Of Contents | >> details >> |
| Keyword | depends List Attribute |
| Purpose | Specifies that the task cannot start before the specified tasks have been finished. By using the 'depends' attribute, the scheduling policy is automatically set to ASAP. If both depends and precedes are used, the last policy counts. |
|
| Syntax | depends (<ABSOLUTE ID> | <ID> | <RELATIVE ID>) [{ <attributes> }] [, (<ABSOLUTE ID> | <ID> | <RELATIVE ID>) [[, ... ]]...] |
|
| Arguments | ABSOLUTE ID [ABSOLUTE_ID] | A reference using the full qualified ID of a task. The IDs of all enclosing parent tasks must be prepended to the task ID and separated with a dot, e.g. proj.plan.doc. |
| ID | Just the ID of the task without any parent IDs. |
|
| RELATIVE ID | A relative task ID always starts with one or more exclamation marks and is followed by a task ID. Each exclamation mark lifts the scope where the ID is looked for to the enclosing task. The ID may contain some of the parent IDs separated by dots, e. g. !!plan.doc. |
|
| Context | task, supplement (task) | |
| Attributes | gapduration, gaplength, onend, onstart |
project "P" 2007-11-09 - 2007-12-24 {
timezone "America/Denver"
}
task foo1 "foo1" {
task foo2 "foo2" {
start 2007-12-04
milestone
}
task foo3 "foo3" {
depends !foo2
length 1d
}
}
task bar "bar" {
depends foo1.foo2
length 2d
}
task bar1 "bar1" {
depends foo1 { gapduration 2d }, bar { gaplength 1d }
duration 2d
}
| << definitions << | Table Of Contents | >> details >> |