You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by pe...@apache.org on 2009/03/02 19:48:05 UTC
svn commit: r749409 -
/ant/core/branches/ANT_17_BRANCH/docs/manual/CoreTasks/property.html
Author: peterreilly
Date: Mon Mar 2 18:48:04 2009
New Revision: 749409
URL: http://svn.apache.org/viewvc?rev=749409&view=rev
Log:
42946: need to add doc for xml format in 1.7.*
Modified:
ant/core/branches/ANT_17_BRANCH/docs/manual/CoreTasks/property.html
Modified: ant/core/branches/ANT_17_BRANCH/docs/manual/CoreTasks/property.html
URL: http://svn.apache.org/viewvc/ant/core/branches/ANT_17_BRANCH/docs/manual/CoreTasks/property.html?rev=749409&r1=749408&r2=749409&view=diff
==============================================================================
--- ant/core/branches/ANT_17_BRANCH/docs/manual/CoreTasks/property.html (original)
+++ ant/core/branches/ANT_17_BRANCH/docs/manual/CoreTasks/property.html Mon Mar 2 18:48:04 2009
@@ -57,6 +57,10 @@
This also holds for properties loaded from a property file.</p>
<p>A list of predefined properties can be found <a
href="../using.html#built-in-props">here</a>.</p>
+<p>Since Ant 1.7.1 it is possible to load properties defined in xml
+according to <a href="http://java.sun.com/dtd/properties.dtd">Suns DTD</a>,
+if Java5+ is present. For this the name of the file, resource or url has
+to end with <tt>.xml</tt>.</p>
<h4>OpenVMS Users</h4>
<p>With the <code>environment</code> attribute this task will load all defined
@@ -150,22 +154,28 @@
<td align="center" valign="top">No</td>
</tr>
</table>
+
<h3>Parameters specified as nested elements</h3>
<h4>classpath</h4>
<p><code>Property</code>'s <i>classpath</i> attribute is a <a
href="../using.html#path">PATH like structure</a> and can also be set via a nested
<i>classpath</i> element.</p>
+
<h3>Examples</h3>
<pre> <property name="foo.dist" value="dist"/></pre>
<p>sets the property <code>foo.dist</code> to the value "dist".</p>
+
<pre> <property file="foo.properties"/></pre>
<p>reads a set of properties from a file called "foo.properties".</p>
+
<pre> <property url="http://www.mysite.com/bla/props/foo.properties"/></pre>
<p>reads a set of properties from the address "http://www.mysite.com/bla/props/foo.properties".</p>
+
<pre> <property resource="foo.properties"/></pre>
<p>reads a set of properties from a resource called "foo.properties".</p>
<p>Note that you can reference a global properties file for all of your Ant
builds using the following:</p>
+
<pre> <property file="${user.home}/.ant-global.properties"/></pre>
<p>since the "user.home" property is defined by the Java virtual machine
to be your home directory. Where the "user.home" property resolves to in
@@ -185,6 +195,18 @@
Two of the values are shown being echoed.
</p>
+<pre>
+ <property environment="env"/>
+ <property file="${user.name}.properties"/>
+ <property file="${env.STAGE}.properties"/>
+ <property file="build.properties"/>
+</pre>
+<p>This buildfile uses the properties defined in <tt>build.properties</tt>. Regarding to the
+environment variable <tt>STAGE</tt> some or all values could be overwritten, e.g. having
+<tt>STAGE=test</tt> and a <tt>test.properties</tt> you have special values for that (like another
+name for the test server). Finally all these values could be overwritten by personal settings with
+a file per user.</p>
+
<h3>Property Files</h3>
As stated, this task will load in a properties file stored in the file