document <ant>'s behavior when multiple nested <property>s set the same property. PR 45226.

git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@691102 13f79535-47bb-0310-9956-ffa450edef68

docs/manual/CoreTasks/ant.html

@@ -52,6 +52,12 @@ regardless of the setting of <i>inheritAll</i>.  This allows you to
 parameterize your subprojects.  Properties defined on the command line
 cannot be overridden by nested <code>&lt;property&gt;</code> elements.</p>
 
+<p>When more than one nested <code>&lt;property&gt;</code> element
+  would set a property of the same name, the one declared last will
+  win.  This is for backwards compatibility reasons even so it is
+  different from the way <code>&lt;property&gt;</code> tasks in build
+  files behave.</p>
+
 <p>References to data types can also be passed to the new project, but
 by default they are not.  If you set the inheritrefs attribute to
 true, all references will be copied, but they will not override

docs/manual/CoreTasks/antcall.html

@@ -45,6 +45,12 @@ regardless of the setting of <i>inheritAll</i>.  This allows you to
 parameterize your subprojects.  Properties defined on the command line
 can not be overridden by nested <code>&lt;param&gt;</code> elements.</p>
 
+<p>When more than one nested <code>&lt;param&gt;</code> element
+  would set a property of the same name, the one declared last will
+  win.  This is for backwards compatibility reasons even so it is
+  different from the way <code>&lt;property&gt;</code> tasks in build
+  files behave.</p>
+
 <p>Nested <a href="#reference"><i><code>&lt;reference&gt</code>;</i></a> elements can
 be used to copy references from the calling project to the new
 project, optionally under a different id.  References taken from

docs/manual/CoreTasks/subant.html

@@ -355,6 +355,13 @@
       </td></tr>
       <tr><td><blockquote>
         Corresponds to <code>&lt;ant&gt;</code>'s nested <code>&lt;property&gt;</code> element.
+
+<p>When more than one nested <code>&lt;property&gt;</code> element
+  would set a property of the same name, the one declared last will
+  win.  This is for backwards compatibility reasons even so it is
+  different from the way <code>&lt;property&gt;</code> tasks in build
+  files behave.</p>
+
  <!-- Ignore -->
  <!-- Ignore -->