diff --git a/docs/manual/using.html b/docs/manual/using.html index dc941c5f3..62661ebf0 100644 --- a/docs/manual/using.html +++ b/docs/manual/using.html @@ -90,18 +90,25 @@ should react to. For example:
<target name="build-module-A" if="module-A-present"/>
<target name="build-own-fake-module-A" unless="module-A-present"/>+
In the first example, if the module-A-present
+property is set (to any value), the target will be run. In the second
+example, if the module-A-present
property is set
+(again, to any value), the target will not be run.
+
If no if
and no unless
attribute is present,
the target will always be executed.
The optional description
attribute can be used to provide a one-line description of this target, which is printed by the
-projecthelp
-verbose
-debug
It is a good practice to place your tstamp tasks in a so-called initialization target, on which all other targets depend. Make sure that target is always the first one in the depends list of the other targets. In this manual, most initialization targets -have the name "init".
+have the name"init"
.
A target has the following attributes:
No |
-Targets beginning with a hyphen such as "-restart" are valid, and can be used
-to name targets which must not be called directly from the command like.
+Targets beginning with a hyphen such as "-restart"
+are valid, and can be used
+to name targets that should not be called directly from the command line.
A task is a piece of code that can be executed.
@@ -189,7 +199,7 @@ to set thefoo
attribute of this particular task instance.
In another task (written in Java), you can access the instance via
project.getReference("task1")
.
-Note1: If "task1" has not been run yet, then +Note1: If "task1" has not been run yet, then it has not been configured (ie., no attributes have been set), and if it is going to be configured later, anything you've done to the instance may be overwritten.