You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by gi...@apache.org on 2018/05/15 09:22:35 UTC
ant git commit: Bz 53019: clarify the description
Repository: ant
Updated Branches:
refs/heads/master 98bc202ce -> e1ef43249
Bz 53019: clarify the description
Project: http://git-wip-us.apache.org/repos/asf/ant/repo
Commit: http://git-wip-us.apache.org/repos/asf/ant/commit/e1ef4324
Tree: http://git-wip-us.apache.org/repos/asf/ant/tree/e1ef4324
Diff: http://git-wip-us.apache.org/repos/asf/ant/diff/e1ef4324
Branch: refs/heads/master
Commit: e1ef4324937e2ef522197d53e92ef5791733825e
Parents: 98bc202
Author: Gintas Grigelionis <gi...@apache.org>
Authored: Tue May 15 11:21:54 2018 +0200
Committer: Gintas Grigelionis <gi...@apache.org>
Committed: Tue May 15 11:21:54 2018 +0200
----------------------------------------------------------------------
manual/Tasks/import.html | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/ant/blob/e1ef4324/manual/Tasks/import.html
----------------------------------------------------------------------
diff --git a/manual/Tasks/import.html b/manual/Tasks/import.html
index 8a3f982..0cc271e 100644
--- a/manual/Tasks/import.html
+++ b/manual/Tasks/import.html
@@ -52,14 +52,14 @@
<p>If a target in the main file is also present in at least one of the imported files, the one
from the main file takes precedence.</p>
- <p>So if I import for example a <samp>docsbuild.xml</samp> file named <q>builddocs</q>, that
- contains a <q>docs</q> target, I can redefine it in my main buildfile and that is the one that
- will be called. This makes it easy to keep the same target name, so that the overriding target
- is still called by any other targets—in either the main or imported buildfile(s)—for
- which it is a dependency, with a different implementation. The target
- from <samp>docsbuild.xml</samp> is made available by the name <q>builddocs.docs</q>. This
- enables the new implementation to call the old target, thus <em>enhancing</em> it with tasks
- called before or after it.</p>
+ <p>So if I import for example a <samp>docsbuild.xml</samp> file containing a project
+ named <q>builddocs</q> that contains a <q>docs</q> target, I can define a <q>docs</q> target in
+ my main buildfile and that is the one that will be called. This makes it easy to keep the same
+ target name, so that the overriding target is still called by any other targets—in either
+ the main or imported buildfile(s)—for which it is a dependency, with a different
+ implementation. The target from <samp>docsbuild.xml</samp> is made available by the
+ name <q>builddocs.docs</q>. This enables the new implementation to call the old target,
+ thus <em>enhancing</em> it with tasks called before or after it.</p>
<p>If you use the <var>as</var> attribute of the task, its value will be used to prefix the
overridden target's name instead of the <var>name</var> attribute of the <code>project</code>