mirror of
https://github.com/ethauvin/kobalt-doc.git
synced 2025-04-25 20:07:11 -07:00
Clarify dependencies.
This commit is contained in:
parent
9c00f7eaca
commit
d12d7f91e9
1 changed files with 2 additions and 3 deletions
|
@ -474,9 +474,8 @@ The <code>@Task</code> annotation accepts the following attributes:
|
||||||
</p>
|
</p>
|
||||||
<p>
|
<p>
|
||||||
Orderings, controlled by <code>"runBefore"</code> and <code>"runAfter"</code> merely specify an ordering
|
Orderings, controlled by <code>"runBefore"</code> and <code>"runAfter"</code> merely specify an ordering
|
||||||
but do not pull new tasks in. This is how you tell Kobalt "In case task X is run, run my task before it
|
but do not pull new tasks in. This is how you tell Kobalt "In case task the user asks for my task to run,
|
||||||
(or after)". But if task X doesn't run, your task will not be run either (unless it's explicitly requested
|
here is when it should be invoked", but your task will run only if it's explicitly invoked by the user.
|
||||||
by the user).
|
|
||||||
</p>
|
</p>
|
||||||
<p>
|
<p>
|
||||||
Here are a few different scenarios to illustrate how the three attributes work for the task <code>example</code>:
|
Here are a few different scenarios to illustrate how the three attributes work for the task <code>example</code>:
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue