/usr/share/doc/libantelope-java/manual/bk01ch09.html is in libantelope-java-doc 3.5.1-4.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 | <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 9. Tracing Target Execution</title><meta name="generator" content="DocBook XSL Stylesheets V1.79.1"><link rel="home" href="index.html" title="Antelope Users Guide"><link rel="up" href="bk01.html" title="Antelope Users Guide, Version @buildnum@"><link rel="prev" href="bk01ch08.html" title="Chapter 8. Editing the Build File"><link rel="next" href="bk01ch10.html" title="Chapter 10. AntLogger"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 9. Tracing Target Execution</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="bk01ch08.html">Prev</a> </td><th width="60%" align="center">Antelope Users Guide, Version @buildnum@</th><td width="20%" align="right"> <a accesskey="n" href="bk01ch10.html">Next</a></td></tr></table><hr></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="tracing"></a>Chapter 9. Tracing Target Execution</h1></div></div></div>
@style@
<p>
Antelope is put into 'tracing mode' when the "Trace" button is clicked. When in tracing mode, the background of the button panel will be blue. When in tracing mode, clicking the target buttons will not actually execute the target. Instead, the output will show the specific order of execution of tasks performed by the target and targets that the selected target depends on. This is useful for figuring out exactly what a specific target does and the order of operations. To turn off tracing mode, click the "Trace" button a second time.
</p><p>
In general, targets are not parsed below task level, that is, nested task attributes are not displayed. However, two tasks are treated specially as they have a direct bearing on how a target executes. These two tasks are <code class="computeroutput">ant</code> and <code class="computeroutput">antcall</code>. If the trace encounters the <code class="computeroutput">ant</code> task, the <code class="computeroutput">buildfile</code> and <code class="computeroutput">target</code> attributes will be displayed, the build file loaded, and the target traced in that build file. If the trace encounters an <code class="computeroutput">antcall</code> task, the <code class="computeroutput">target</code> attribute will be parsed and the target will be traced.
</p><p>
Here is a sample trace:
</p><p>
</p><pre class="programlisting">
Tracing target: deploy-all
Legend: <target>[task]
<deploy-all>
<clean>[delete]
<deploy-all>[javac deprecation=on debug=on destdir=build srcdir=src
includes=ise/ excludes=ise/antelope/plugin/ includejavaruntime=yes source=1.5]
<deploy-all>[copy todir=build]
<deploy-all>[jar jarfile=/usr/local/java/antelope/Antelope]
</deploy-all>
Done tracing target: deploy-all
</pre><p>
</p><p>
And a line by line explanation:
</p><p>
</p><div class="table"><a name="idm315"></a><p class="title"><b>Table 9.1. Target Trace Example Explanation</b></p><div class="table-contents"><table class="table" summary="Target Trace Example Explanation" border="1"><colgroup><col><col></colgroup><tbody><tr><td>Tracing target: deploy-all</td><td>The trace is going to trace the deploy-all target.</td></tr><tr><td>Legend: <target>[task]</td><td>Targets shown with angle brackets, tasks with square brackets.</td></tr><tr><td><deploy-all></td><td>The trace is starting on the deploy-all target.</td></tr><tr><td><clean>[delete]</td><td>The deploy-all target depends on the clean target, which performs a 'delete' task.</td></tr><tr><td><deploy-all>[javac deprecation=on debug=on destdir=build srcdir=src includes=ise/ excludes=ise/antelope/plugin/ includejavaruntime=yes source=1.5]</td><td>The deploy-all target executes a 'javac' task. The parameters for the task are shown.</td></tr><tr><td><deploy-all>[copy todir=build]</td><td>The deploy-all target executes a 'copy' tasks. Most likely, this tasks has nested includes and/or excludes, which are not shown in the trace.</td></tr><tr><td><deploy-all>[jar jarfile=/usr/local/java/antelope/Antelope]</td><td>The deploy-all target executes the 'jar' task.</td></tr><tr><td></deploy-all></td><td>The trace has reached the end of the deploy-all target.</td></tr><tr><td>Done tracing target: deploy-all</td><td>Obviously, the trace is done.</td></tr></tbody></table></div></div><p><br class="table-break">
</p><p>
So the 'deploy_all' target first causes the 'clean' target to execute a 'delete' task, then causes the 'compile' target to execute a 'javac' task, and finally causes the 'deploy' target to create a jar file.
</p><p>
</p><div class="figure"><a name="idm348"></a><p class="title"><b>Figure 9.1. Antelope in 'Trace' Mode</b></p><div class="figure-contents"><img src="tracemode.gif" alt="Antelope in 'Trace' Mode"></div></div><p><br class="figure-break">
</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="bk01ch08.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="bk01.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="bk01ch10.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 8. Editing the Build File </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 10. AntLogger</td></tr></table></div></body></html>
|