From 40cfb498fd7ea0daa912d9d10b6634f0a8215a64 Mon Sep 17 00:00:00 2001
From: Steve Loughran <stevel@apache.org>
Date: Sat, 2 Oct 2004 23:39:59 +0000
Subject: [PATCH] clarify conditional target execution logic

git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@276909 13f79535-47bb-0310-9956-ffa450edef68
---
 docs/manual/using.html | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/docs/manual/using.html b/docs/manual/using.html
index 0106de405..d9e39286a 100644
--- a/docs/manual/using.html
+++ b/docs/manual/using.html
@@ -107,6 +107,14 @@ example, if the <code>module-A-present</code> property is set
 </p>
 <p>If no <code>if</code> and no <code>unless</code> attribute is present,
 the target will always be executed.</p>
+
+<p>
+<b>Important:</b> the <code>if</code> and <code>unless</code> attributes only 
+enable or disable the target to which they are attached. They do not control
+whether or not targets that a conditional target depends upon get executed. 
+In fact, they do not even get evaluated until the target is about to be executed,
+and all its predecessors have already run.
+
 <p>The optional <code>description</code> attribute can be used to provide a one-line description of this target, which is printed by the
 <nobr><code>-projecthelp</code></nobr> command-line option. Targets
 without such a description are deemed internal and will not be listed,