<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>command line arguments in ANt Archives - scmGalaxy</title>
	<atom:link href="https://www.scmgalaxy.com/tutorials/tag/command-line-arguments-in-ant/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.scmgalaxy.com/tutorials/tag/command-line-arguments-in-ant/</link>
	<description>A Platform for Software Engineers</description>
	<lastBuildDate>Sat, 27 Feb 2021 09:55:34 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1</generator>
	<item>
		<title>Understand Ant command line arguments with Examples</title>
		<link>https://www.scmgalaxy.com/tutorials/ant-command-line-arguments-2/</link>
					<comments>https://www.scmgalaxy.com/tutorials/ant-command-line-arguments-2/#respond</comments>
		
		<dc:creator><![CDATA[scmgalaxy K]]></dc:creator>
		<pubDate>Tue, 06 Oct 2009 11:36:10 +0000</pubDate>
				<category><![CDATA[Apache Ant]]></category>
		<category><![CDATA[ANT]]></category>
		<category><![CDATA[Ant command line arguments]]></category>
		<category><![CDATA[Ant command line arguments Examples]]></category>
		<category><![CDATA[Arguments]]></category>
		<category><![CDATA[Command line]]></category>
		<category><![CDATA[command line arguments in ANt]]></category>
		<category><![CDATA[command-line argument]]></category>
		<category><![CDATA[Examples]]></category>
		<category><![CDATA[Guide]]></category>
		<category><![CDATA[How to pass ant command line arguments]]></category>
		<category><![CDATA[Reference]]></category>
		<category><![CDATA[Resource]]></category>
		<category><![CDATA[Tutorial]]></category>
		<category><![CDATA[Understand]]></category>
		<guid isPermaLink="false">http://www.scmgalaxy.com/tutorials/2009/10/06/ant-command-line-arguments-2/</guid>

					<description><![CDATA[<p>Several tasks take arguments that will be passed to another process on the command line. To make it easier to [&#8230;]</p>
<p>The post <a href="https://www.scmgalaxy.com/tutorials/ant-command-line-arguments-2/">Understand Ant command line arguments with Examples</a> appeared first on <a href="https://www.scmgalaxy.com/tutorials">scmGalaxy</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><img fetchpriority="high" decoding="async" class="alignnone size-full wp-image-4073 aligncenter" src="https://www.scmgalaxy.com/tutorials/wp-content/uploads/2009/10/ant-command-line-arguments.png" alt="ant-command-line-arguments" width="600" height="400" srcset="https://www.scmgalaxy.com/tutorials/wp-content/uploads/2009/10/ant-command-line-arguments.png 600w, https://www.scmgalaxy.com/tutorials/wp-content/uploads/2009/10/ant-command-line-arguments-300x200.png 300w" sizes="(max-width: 600px) 100vw, 600px" /></p>
<p><strong>Several tasks take arguments that will be passed to another process on the command line. To make it easier to specify arguments that contain space characters, nested arg elements can be used.</strong></p>
<p><strong>value</strong> &#8211; a single command-line argument; can contain space characters.</p>
<p><strong>file </strong>&#8211; The name of a file as a single command-line argument; will be replaced with the absolute filename of the file.</p>
<p><strong>path</strong> &#8211; A string that will be treated as a path-like string as a single command-line argument; you can use ; or : as path separators and Ant will convert it to the platform&#8217;s local conventions.</p>
<p><strong>pathref</strong> &#8211; Reference to a path defined elsewhere. Ant will convert it to the platform&#8217;s local conventions.</p>
<p><strong>line</strong> &#8211; a space-delimited list of command-line arguments.</p>
<p>It is highly recommended to avoid the line version when possible. Ant will try to split the command line in a way similar to what a (Unix) shell would do, but may create something that is very different from what you expect under some circumstances.</p>
<p><strong>Examples</strong></p>
<p>&lt;arg value=&#8221;-l -a&#8221;/&gt;</p>
<p>is a single command-line argument containing a space character.</p>
<p>&lt;arg line=&#8221;-l -a&#8221;/&gt;</p>
<p>represents two separate command-line arguments.</p>
<p>&lt;arg path=&#8221;/dir;/dir2:\dir3&#8243;/&gt;</p>
<p>is a single command-line argument with the value \dir;\dir2;\dir3 on DOS-based systems and /dir:/dir2:/dir3 on Unix-like systems.</p>
<p>Command-line Options Summary<br />
ant [options] [target [target2 [target3] &#8230;]]</p>
<table style="border-collapse: collapse; width: 310pt;" border="2" width="414" cellspacing="0" cellpadding="0">
<colgroup>
<col style="width: 74pt;" width="99" />
<col style="width: 236pt;" width="315" /></colgroup>
<tbody>
<tr style="height: 15.75pt;">
<td class="xl65" style="height: 15.75pt; width: 74pt;" width="99" height="21"><strong>Options:</strong></td>
<td class="xl66" style="border-left: medium none; width: 236pt;" width="315"></td>
</tr>
<tr style="height: 15.75pt;">
<td class="xl67" style="border-top: medium none; height: 15.75pt; padding-bottom: 0in; padding-top: 0in;" height="21">-help, -h</td>
<td class="xl67" style="border-top: medium none; border-left: medium none; padding-bottom: 0in; padding-top: 0in;">Displays help information describing the Ant command and its options</td>
</tr>
<tr style="height: 15.75pt;">
<td class="xl67" style="border-top: medium none; height: 15.75pt; padding-bottom: 0in; padding-top: 0in;" height="21">-projecthelp, -p</td>
<td class="xl67" style="border-top: medium none; border-left: medium none; padding-bottom: 0in; padding-top: 0in;">Print project help information</td>
</tr>
<tr style="height: 15.75pt;">
<td class="xl67" style="border-top: medium none; height: 15.75pt; padding-bottom: 0in; padding-top: 0in;" height="21">-version</td>
<td class="xl67" style="border-top: medium none; border-left: medium none; padding-bottom: 0in; padding-top: 0in;">Print the version information and exit</td>
</tr>
<tr style="height: 15.75pt;">
<td class="xl67" style="border-top: medium none; height: 15.75pt; padding-bottom: 0in; padding-top: 0in;" height="21">-diagnostics</td>
<td class="xl67" style="border-top: medium none; border-left: medium none; padding-bottom: 0in; padding-top: 0in;">Print information that might be helpful to diagnose or report problems.</td>
</tr>
<tr style="height: 15.75pt;">
<td class="xl67" style="border-top: medium none; height: 15.75pt; padding-bottom: 0in; padding-top: 0in;" height="21">-quiet, -q</td>
<td class="xl67" style="border-top: medium none; border-left: medium none; padding-bottom: 0in; padding-top: 0in;">Suppresses most messages not originated by an echo task in the buildfile</td>
</tr>
<tr style="height: 15.75pt;">
<td class="xl67" style="border-top: medium none; height: 15.75pt; padding-bottom: 0in; padding-top: 0in;" height="21">-verbose, -v</td>
<td class="xl67" style="border-top: medium none; border-left: medium none; padding-bottom: 0in; padding-top: 0in;">Displays detailed messages for every operation during a build.</td>
</tr>
<tr style="height: 15.75pt;">
<td class="xl67" style="border-top: medium none; height: 15.75pt; padding-bottom: 0in; padding-top: 0in;" height="21">-debug, -d</td>
<td class="xl67" style="border-top: medium none; border-left: medium none; padding-bottom: 0in; padding-top: 0in;">Print debugging information</td>
</tr>
<tr style="height: 15.75pt;">
<td class="xl67" style="border-top: medium none; height: 15.75pt; padding-bottom: 0in; padding-top: 0in;" height="21">-emacs, -e</td>
<td class="xl67" style="border-top: medium none; border-left: medium none; padding-bottom: 0in; padding-top: 0in;">Produce logging information without adornments</td>
</tr>
<tr style="height: 15.75pt;">
<td class="xl67" style="border-top: medium none; height: 15.75pt; padding-bottom: 0in; padding-top: 0in;" height="21">-lib &lt;path&gt;</td>
<td class="xl67" style="border-top: medium none; border-left: medium none; padding-bottom: 0in; padding-top: 0in;">Specifies a path to search for jars and classes</td>
</tr>
<tr style="height: 15.75pt;">
<td class="xl67" style="border-top: medium none; height: 15.75pt; padding-bottom: 0in; padding-top: 0in;" height="21">-logfile &lt;file&gt;</td>
<td class="xl67" style="border-top: medium none; border-left: medium none; padding-bottom: 0in; padding-top: 0in;">Use given file for log</td>
</tr>
<tr style="height: 15.75pt;">
<td class="xl67" style="border-top: medium none; height: 15.75pt; padding-bottom: 0in; padding-top: 0in;" height="21">-l &lt;file&gt;</td>
<td class="xl67" style="border-top: medium none; border-left: medium none; padding-bottom: 0in; padding-top: 0in;">Use given file for log</td>
</tr>
<tr style="height: 15.75pt;">
<td class="xl67" style="border-top: medium none; height: 15.75pt; padding-bottom: 0in; padding-top: 0in;" height="21">-logger &lt;classname&gt;</td>
<td class="xl67" style="border-top: medium none; border-left: medium none; padding-bottom: 0in; padding-top: 0in;">Specifies a class to handle Ant logging.</td>
</tr>
<tr style="height: 15.75pt;">
<td class="xl67" style="border-top: medium none; height: 15.75pt; padding-bottom: 0in; padding-top: 0in;" height="21">-listener &lt;classname&gt;</td>
<td class="xl67" style="border-top: medium none; border-left: medium none; padding-bottom: 0in; padding-top: 0in;">Add an instance of class as a project listener</td>
</tr>
<tr style="height: 15.75pt;">
<td class="xl67" style="border-top: medium none; height: 15.75pt; padding-bottom: 0in; padding-top: 0in;" height="21">-noinput</td>
<td class="xl67" style="border-top: medium none; border-left: medium none; padding-bottom: 0in; padding-top: 0in;">Do not allow interactive input</td>
</tr>
<tr style="height: 15.75pt;">
<td class="xl67" style="border-top: medium none; height: 15.75pt; padding-bottom: 0in; padding-top: 0in;" height="21">-buildfile &lt;file&gt;</td>
<td class="xl67" style="border-top: medium none; border-left: medium none; padding-bottom: 0in; padding-top: 0in;">Use given buildfile</td>
</tr>
<tr style="height: 15.75pt;">
<td class="xl67" style="border-top: medium none; height: 15.75pt; padding-bottom: 0in; padding-top: 0in;" height="21">-file &lt;file&gt;</td>
<td class="xl67" style="border-top: medium none; border-left: medium none; padding-bottom: 0in; padding-top: 0in;">Use given buildfile</td>
</tr>
<tr style="height: 15.75pt;">
<td class="xl67" style="border-top: medium none; height: 15.75pt; padding-bottom: 0in; padding-top: 0in;" height="21">-f &lt;file&gt;</td>
<td class="xl67" style="border-top: medium none; border-left: medium none; padding-bottom: 0in; padding-top: 0in;">Use given buildfile</td>
</tr>
<tr style="height: 15.75pt;">
<td class="xl67" style="border-top: medium none; height: 15.75pt; padding-bottom: 0in; padding-top: 0in;" height="21">-D&lt;property&gt;=&lt;value&gt;</td>
<td class="xl67" style="border-top: medium none; border-left: medium none; padding-bottom: 0in; padding-top: 0in;">Defines a property name-value pair on the command line.</td>
</tr>
<tr style="height: 15.75pt;">
<td class="xl67" style="border-top: medium none; height: 15.75pt; padding-bottom: 0in; padding-top: 0in;" height="21">-keep-going, -k</td>
<td class="xl67" style="border-top: medium none; border-left: medium none; padding-bottom: 0in; padding-top: 0in;">execute all targets that do not depend on failed target(s)</td>
</tr>
<tr style="height: 15.75pt;">
<td class="xl67" style="border-top: medium none; height: 15.75pt; padding-bottom: 0in; padding-top: 0in;" height="21">-propertyfile &lt;name&gt;</td>
<td class="xl67" style="border-top: medium none; border-left: medium none; padding-bottom: 0in; padding-top: 0in;">load all properties from file with -D properties taking precedence</td>
</tr>
<tr style="height: 15.75pt;">
<td class="xl67" style="border-top: medium none; height: 15.75pt; padding-bottom: 0in; padding-top: 0in;" height="21">-inputhandler &lt;class&gt;</td>
<td class="xl67" style="border-top: medium none; border-left: medium none; padding-bottom: 0in; padding-top: 0in;">the class which will handle input requests</td>
</tr>
<tr style="height: 15.75pt;">
<td class="xl67" style="border-top: medium none; height: 15.75pt; padding-bottom: 0in; padding-top: 0in;" height="21">-find &lt;file&gt;</td>
<td class="xl67" style="border-top: medium none; border-left: medium none; padding-bottom: 0in; padding-top: 0in;">Search for buildfile towards the root of the filesystem and use it</td>
</tr>
</tbody>
</table>
<p>The post <a href="https://www.scmgalaxy.com/tutorials/ant-command-line-arguments-2/">Understand Ant command line arguments with Examples</a> appeared first on <a href="https://www.scmgalaxy.com/tutorials">scmGalaxy</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.scmgalaxy.com/tutorials/ant-command-line-arguments-2/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Ant command line arguments &#8211; Examples &#8211; Summary</title>
		<link>https://www.scmgalaxy.com/tutorials/ant-command-line-arguments/</link>
					<comments>https://www.scmgalaxy.com/tutorials/ant-command-line-arguments/#comments</comments>
		
		<dc:creator><![CDATA[scmgalaxy K]]></dc:creator>
		<pubDate>Sat, 20 Jun 2009 04:04:31 +0000</pubDate>
				<category><![CDATA[Apache Ant]]></category>
		<category><![CDATA[ANT]]></category>
		<category><![CDATA[Ant command line arguments]]></category>
		<category><![CDATA[Ant command line arguments Examples]]></category>
		<category><![CDATA[Arguments]]></category>
		<category><![CDATA[Command line]]></category>
		<category><![CDATA[command line arguments in ANt]]></category>
		<category><![CDATA[command-line argument]]></category>
		<category><![CDATA[Examples]]></category>
		<category><![CDATA[Guide]]></category>
		<category><![CDATA[How to pass ant command line arguments]]></category>
		<category><![CDATA[Reference]]></category>
		<category><![CDATA[Resource]]></category>
		<category><![CDATA[Tutorial]]></category>
		<guid isPermaLink="false">http://www.scmgalaxy.com/tutorials/2009/06/20/ant-command-line-arguments/</guid>

					<description><![CDATA[<p>Ant command line arguments Several tasks take arguments that will be passed to another process on the command line. To [&#8230;]</p>
<p>The post <a href="https://www.scmgalaxy.com/tutorials/ant-command-line-arguments/">Ant command line arguments &#8211; Examples &#8211; Summary</a> appeared first on <a href="https://www.scmgalaxy.com/tutorials">scmGalaxy</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><img decoding="async" class="alignnone size-full wp-image-4015 aligncenter" src="https://www.scmgalaxy.com/tutorials/wp-content/uploads/2009/06/ant-command-line-arguments.png" alt="ant-command-line-arguments" width="600" height="400" srcset="https://www.scmgalaxy.com/tutorials/wp-content/uploads/2009/06/ant-command-line-arguments.png 600w, https://www.scmgalaxy.com/tutorials/wp-content/uploads/2009/06/ant-command-line-arguments-300x200.png 300w" sizes="(max-width: 600px) 100vw, 600px" /></p>
<table border="0" width="100%">
<tbody>
<tr>
<td class="HEADING"><strong>Ant command line arguments</strong></td>
</tr>
<tr>
<td class="HEADING_BODY">Several tasks take arguments that will be passed to another process on the command line. To make it easier to specify arguments that contain space characters, nested arg elements can be used.</p>
<p><strong><em>value</em></strong> &#8211; a single command-line argument; can contain space characters.<br />
<strong><em>file</em></strong><em> &#8211; </em>The name of a file as a single command-line argument; will be replaced with the absolute filename of the file.<br />
<strong><em>path</em></strong><em> &#8211; </em>A string that will be treated as a path-like string as a single command-line argument; you can use ; or : as path separators and Ant will convert it to the platform&#8217;s local conventions.<br />
<strong><em>pathref</em></strong><em> &#8211;</em> Reference to a path defined elsewhere. Ant will convert it to the platform&#8217;s local conventions.<br />
<strong><em>line </em></strong><em>&#8211; </em>a space-delimited list of command-line arguments.</p>
<p>It is highly recommended to avoid the line version when possible. Ant will try to split the command line in a way similar to what a (Unix) shell would do, but may create something that is very different from what you expect under some circumstances.</td>
</tr>
<tr>
<td class="HEADING"><strong>Examples</strong></td>
</tr>
<tr>
<td class="HEADING_BODY">&lt;arg value=&#8221;-l -a&#8221;/&gt;<br />
is a single command-line argument containing a space character.<br />
&lt;arg line=&#8221;-l -a&#8221;/&gt;<br />
represents two separate command-line arguments.<br />
&lt;arg path=&#8221;/dir;/dir2:\dir3&#8243;/&gt;<br />
is a single command-line argument with the value \dir;\dir2;\dir3 on DOS-based systems and /dir:/dir2:/dir3 on Unix-like systems.</td>
</tr>
<tr>
<td class="HEADING"><strong>Command-line Options Summary</strong></td>
</tr>
<tr>
<td class="HEADING_BODY">ant [options] [target [target2 [target3] &#8230;]]</p>
<p>Options:</p>
<table border="0" width="100%" cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td>-help, -h</td>
<td>Displays help information describing the Ant command and its options</td>
</tr>
<tr>
<td>-projecthelp, -p</td>
<td>Print project help information</td>
</tr>
<tr>
<td>-version</td>
<td>Print the version information and exit</td>
</tr>
<tr>
<td>-diagnostics</td>
<td>Print information that might be helpful to diagnose or report problems.</td>
</tr>
<tr>
<td>-quiet, -q</td>
<td>Suppresses most messages not originated by an echo task in the buildfile</td>
</tr>
<tr>
<td>-verbose, -v</td>
<td>Displays detailed messages for every operation during a build.</td>
</tr>
<tr>
<td>-debug, -d</td>
<td>Print debugging information</td>
</tr>
<tr>
<td>-emacs, -e</td>
<td>Produce logging information without adornments</td>
</tr>
<tr>
<td>-lib &lt;path&gt;</td>
<td>Specifies a path to search for jars and classes</td>
</tr>
<tr>
<td>-logfile &lt;file&gt;</td>
<td>Use given file for log</td>
</tr>
<tr>
<td>-l &lt;file&gt;</td>
<td>Use given file for log</td>
</tr>
<tr>
<td>-logger &lt;classname&gt;</td>
<td>Specifies a class to handle Ant logging.</td>
</tr>
<tr>
<td>-listener &lt;classname&gt;</td>
<td>Add an instance of class as a project listener</td>
</tr>
<tr>
<td>-noinput</td>
<td>Do not allow interactive input</td>
</tr>
<tr>
<td>-buildfile &lt;file&gt;</td>
<td>Use given buildfile</td>
</tr>
<tr>
<td>-file &lt;file&gt;</td>
<td>Use given buildfile</td>
</tr>
<tr>
<td>-f &lt;file&gt;</td>
<td>Use given buildfile</td>
</tr>
<tr>
<td>-D&lt;property&gt;=&lt;value&gt;</td>
<td>Defines a property name-value pair on the command line.</td>
</tr>
<tr>
<td>-keep-going, -k</td>
<td>execute all targets that do not depend on failed target(s)</td>
</tr>
<tr>
<td>-propertyfile &lt;name&gt;</td>
<td>load all properties from file with -D properties taking precedence</td>
</tr>
<tr>
<td>-inputhandler &lt;class&gt;</td>
<td>the class which will handle input requests</td>
</tr>
<tr>
<td>-find &lt;file&gt;</td>
<td>Search for buildfile towards the root of the filesystem and use it</td>
</tr>
</tbody>
</table>
</td>
</tr>
<tr>
<td class="HEADING_BODY"></td>
</tr>
</tbody>
</table>
<p>The post <a href="https://www.scmgalaxy.com/tutorials/ant-command-line-arguments/">Ant command line arguments &#8211; Examples &#8211; Summary</a> appeared first on <a href="https://www.scmgalaxy.com/tutorials">scmGalaxy</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.scmgalaxy.com/tutorials/ant-command-line-arguments/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
	</channel>
</rss>
