From a9b1c6e9621a6f910dfdf7d27c9aa551352ea0d0 Mon Sep 17 00:00:00 2001
From: Stefan Bodewig
<property>
elements.
+parameterize your subprojects.
When more than one nested <property>
element
would set a property of the same name, the one declared last will
@@ -58,6 +57,17 @@ cannot be overridden by nested <property>
elements.
<property>
tasks in build
files behave.
+Properties defined on the command line cannot be overridden by
+ nested <property>
elements. Since Ant
+ 1.8.0. the same is true for nested structures
+ of <ant>
tasks: if a build file A
+ invokes B via an <ant>
task setting a
+ property with a nested <property>
element
+ and B contains an <ant>
tasks
+ invoking C, C will see the value set
+ in A, even if B used a
+ nested <property>
element as well.
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 diff --git a/docs/manual/Tasks/subant.html b/docs/manual/Tasks/subant.html index 74699642f..f9b66bd6d 100644 --- a/docs/manual/Tasks/subant.html +++ b/docs/manual/Tasks/subant.html @@ -72,6 +72,11 @@ part of.
Since Ant 1.6
+ +subant
uses ant
internally so many things
+ said in ant
's manual page apply
+ here as well.