From d12d7f91e9dcabce7131f47a601017b4382b3a44 Mon Sep 17 00:00:00 2001 From: Cedric Beust Date: Wed, 15 Jun 2016 01:03:07 -0800 Subject: [PATCH] Clarify dependencies. --- plug-in-development/index.html | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/plug-in-development/index.html b/plug-in-development/index.html index 13d014d..27b2562 100644 --- a/plug-in-development/index.html +++ b/plug-in-development/index.html @@ -474,9 +474,8 @@ The @Task annotation accepts the following attributes:

Orderings, controlled by "runBefore" and "runAfter" 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 - (or after)". But if task X doesn't run, your task will not be run either (unless it's explicitly requested - by the user). + but do not pull new tasks in. This is how you tell Kobalt "In case task the user asks for my task to run, + here is when it should be invoked", but your task will run only if it's explicitly invoked by the user.

Here are a few different scenarios to illustrate how the three attributes work for the task example: