You can not select more than 25 topics Topics must start with a chinese character,a letter or number, can include dashes ('-') and can be up to 35 characters long.

problems.html 27 kB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506
  1. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
  2. <html>
  3. <!-- GENERATED FILE, DO NOT EDIT, EDIT THE XML FILE IN xdocs INSTEAD! -->
  4. <head>
  5. <META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
  6. <title>Apache Ant - Having Problems?</title>
  7. <link type="text/css" href="page.css" rel="stylesheet">
  8. <meta name="author" value="Conor MacNeill">
  9. <meta name="email" value="">
  10. </head>
  11. <body marginheight="0" marginwidth="0" topmargin="0" leftmargin="0" text="#000000" bgcolor="#ffffff">
  12. <table summary="navigation path" width="100%" border="0" cellpadding="0" cellspacing="0">
  13. <tr>
  14. <td nowrap="nowrap" valign="middle" bgcolor="#CFDCED" height="20"><img height="1" width="5" alt="" border="0" src="images/spacer.gif"><font size="2" face="Arial, Helvetica, Sans-serif"><script src="breadcrumbs.js" language="JavaScript" type="text/javascript"></script></font></td>
  15. </tr>
  16. <tr>
  17. <td bgcolor="#4C6C8F" height="2"><img height="2" width="2" alt="" border="0" src="images/spacer.gif"></td>
  18. </tr>
  19. </table>
  20. <table summary="header with logos" width="100%" border="0" cellpadding="0" cellspacing="0">
  21. <tr>
  22. <td bgcolor="#294563"><a href="http://ant.apache.org/"><img border="0" alt="Apache XML logo" src="images/group-logo.gif"></a></td><td width="100%" align="center" bgcolor="#294563"><a href="http://ant.apache.org/"><img alt="Apache XML site" border="0" src="images/project-logo.gif"></a></td><td valign="top" rowspan="2" bgcolor="#294563">
  23. <form target="_blank" onsubmit="q.value = query.value + ' site:ant.apache.org'" action="http://www.google.com/search" method="get">
  24. <table summary="search" border="0" cellspacing="0" cellpadding="0" bgcolor="#4C6C8F">
  25. <tr>
  26. <td colspan="3"><img height="10" width="1" alt="" src="images/spacer.gif"></td>
  27. </tr>
  28. <tr>
  29. <td><img height="1" width="1" alt="" src="images/spacer.gif"></td><td nowrap="nowrap"><input name="q" type="hidden"><input size="15" id="query" type="text"><img height="1" width="5" alt="" src="images/spacer.gif"><input name="Search" value="Search" type="submit">
  30. <br>
  31. <font face="Arial, Helvetica, Sans-serif" size="2" color="white">
  32. the Apache Ant site
  33. </font></td><td><img height="1" width="1" alt="" src="images/spacer.gif"></td>
  34. </tr>
  35. <tr>
  36. <td><img alt="" border="0" height="10" width="9" src="images/search-left.gif"></td><td><img height="1" width="1" alt="" src="images/spacer.gif"></td><td><img alt="" border="0" height="10" width="9" src="images/search-right.gif"></td>
  37. </tr>
  38. </table>
  39. </form>
  40. </td><td bgcolor="#294563"><img height="10" width="10" alt="" src="images/spacer.gif"></td>
  41. </tr>
  42. <tr>
  43. <td valign="bottom" bgcolor="#294563" colspan="2">
  44. <div class="tab">
  45. <table summary="tab bar" border="0" cellpadding="0" cellspacing="0">
  46. <tr>
  47. <td width="8"><img alt="" height="8" width="8" src="images/spacer.gif"></td><td valign="bottom">
  48. <table summary="selected tab" height="30" border="0" cellpadding="0" cellspacing="0">
  49. <tr>
  50. <td valign="top" width="5" bgcolor="#4C6C8F"><img height="5" width="5" alt="" src="images/tabSel-left.gif"></td><td valign="middle" bgcolor="#4C6C8F"><font color="#ffffff" size="2" face="Arial, Helvetica, Sans-serif"><b>Home</b></font></td><td valign="top" width="5" bgcolor="#4C6C8F"><img height="5" width="5" alt="" src="images/tabSel-right.gif"></td>
  51. </tr>
  52. </table>
  53. </td>
  54. </tr>
  55. </table>
  56. </div>
  57. </td><td bgcolor="#294563"><img alt="" width="1" height="1" src="images/spacer.gif"></td>
  58. </tr>
  59. <tr>
  60. <td bgcolor="#4C6C8F" colspan="4"><img width="1" height="10" alt="" src="images/spacer.gif"></td>
  61. </tr>
  62. </table>
  63. <table summary="page content" bgcolor="#ffffff" width="100%" border="0" cellpadding="0" cellspacing="0">
  64. <tr>
  65. <td valign="top">
  66. <table summary="menu" border="0" cellspacing="0" cellpadding="0">
  67. <tr>
  68. <td rowspan="3" valign="top">
  69. <table summary="blue line" border="0" cellpadding="0" cellspacing="0">
  70. <tr>
  71. <td bgcolor="#294563"><img width="10" height="1" alt="" src="images/spacer.gif"></td>
  72. </tr>
  73. <tr>
  74. <td bgcolor="#CFDCED"><font color="#4C6C8F" size="4" face="Arial, Helvetica, Sans-serif">&nbsp;</font></td>
  75. </tr>
  76. <tr>
  77. <td bgcolor="#294563"><img width="10" height="1" alt="" src="images/spacer.gif"></td>
  78. </tr>
  79. </table>
  80. </td><td bgcolor="#294563"><img width="1" height="1" alt="" src="images/spacer.gif"></td><td valign="bottom" bgcolor="#4C6C8F"><img width="10" height="10" alt="" src="images/spacer.gif"></td><td nowrap="nowrap" valign="top" bgcolor="#4C6C8F">
  81. <div class="menu"><ul>
  82. <li><font color="#CFDCED">Apache Ant</font>
  83. <ul>
  84. <li>
  85. <a href="./index.html">Welcome</a>
  86. </li>
  87. <li>
  88. <a href="./license.html">License</a>
  89. </li>
  90. <li>
  91. <a href="./antnews.html">News</a>
  92. </li>
  93. </ul>
  94. </li>
  95. <li><font color="#CFDCED">Documentation</font>
  96. <ul>
  97. <li>
  98. <a href="./manual/index.html">Manual</a>
  99. </li>
  100. <li>
  101. <a href="./projects.html">Related Projects</a>
  102. </li>
  103. <li>
  104. <a href="./external.html">External Tools and Tasks</a>
  105. </li>
  106. <li>
  107. <a href="./resources.html">Resources</a>
  108. </li>
  109. <li>
  110. <a href="./faq.html">Frequently Asked Questions</a>
  111. </li>
  112. <li>
  113. <span class="sel"><font color="#ffcc00">Having Problems?</font></span>
  114. </li>
  115. </ul>
  116. </li>
  117. <li><font color="#CFDCED">Download</font>
  118. <ul>
  119. <li>
  120. <a href="./bindownload.cgi">Binary Distributions</a>
  121. </li>
  122. <li>
  123. <a href="./srcdownload.cgi">Source Distributions</a>
  124. </li>
  125. </ul>
  126. </li>
  127. <li><font color="#CFDCED">Get Involved</font>
  128. <ul>
  129. <li>
  130. <a href="./mail.html">Mailing Lists</a>
  131. </li>
  132. <li>
  133. <a href="./cvs.html">CVS Repositories</a>
  134. </li>
  135. <li>
  136. <a href="http://nagoya.apache.org/bugzilla/enter_bug.cgi?product=Ant">Bug Database</a>
  137. </li>
  138. <li>
  139. <a href="http://nagoya.apache.org/bugzilla/enter_bug.cgi?product=Ant&bug_severity=Enhancement">Enhancement Requests</a>
  140. </li>
  141. </ul>
  142. </li>
  143. <li><font color="#CFDCED">Project Management</font>
  144. <ul>
  145. <li>
  146. <a href="./contributors.html">Contributors</a>
  147. </li>
  148. <li>
  149. <a href="./mission.html">Apache Ant Mission</a>
  150. </li>
  151. <li>
  152. <a href="./guidelines.html">Project Guidelines</a>
  153. </li>
  154. <li>
  155. <a href="./legal.html">Legal</a>
  156. </li>
  157. </ul>
  158. </li>
  159. </ul>
  160. </td><td valign="bottom" bgcolor="#4C6C8F"><img width="10" height="10" alt="" src="images/spacer.gif"></td><td bgcolor="#294563"><img width="1" height="1" alt="" src="images/spacer.gif"></td>
  161. </tr>
  162. <tr>
  163. <td valign="bottom" align="left" colspan="2" rowspan="2" bgcolor="#4C6C8F"><img height="10" width="10" border="0" alt="" src="images/menu-left.gif"></td><td bgcolor="#4C6C8F"><img height="10" width="10" border="0" alt="" src="images/spacer.gif"></td><td valign="bottom" align="right" colspan="2" rowspan="2" bgcolor="#4C6C8F"><img height="10" width="10" border="0" alt="" src="images/menu-right.gif"></td>
  164. </tr>
  165. <tr>
  166. <td height="1" bgcolor="#294563"><img width="1" height="1" alt="" src="images/spacer.gif"></td>
  167. </tr>
  168. </table>
  169. </td><td valign="top" width="100%">
  170. <table summary="content" width="100%" border="0" cellpadding="0" cellspacing="0">
  171. <tr>
  172. <td colspan="4" bgcolor="#294563"><img width="10" height="1" alt="" src="images/spacer.gif"></td>
  173. </tr>
  174. <tr>
  175. <td align="left" width="10" bgcolor="#CFDCED"><img width="10" height="1" alt="" src="images/spacer.gif"></td><td align="left" width="50%" bgcolor="#CFDCED"><font color="#4C6C8F" size="3" face="Arial, Helvetica, Sans-serif">
  176. &nbsp;
  177. </font><img width="10" height="8" alt="" src="images/spacer.gif"></td><td align="right" width="50%" bgcolor="#CFDCED"><font color="#4C6C8F" size="3" face="Arial, Helvetica, Sans-serif">
  178. &nbsp;
  179. </font><img width="10" height="8" alt="" src="images/spacer.gif"></td><td width="10" bgcolor="#CFDCED"><img width="10" height="1" alt="" src="images/spacer.gif"></td>
  180. </tr>
  181. <tr>
  182. <td colspan="4" bgcolor="#294563"><img width="10" height="1" alt="" src="images/spacer.gif"></td>
  183. </tr>
  184. <tr>
  185. <td align="left" width="10"><img width="10" height="1" alt="" src="images/spacer.gif"></td><td align="left" width="100%">
  186. <div class="content">
  187. <table class="title">
  188. <tr>
  189. <td valign="middle">
  190. <h1>Having Problems?</h1>
  191. </td>
  192. </tr>
  193. </table>
  194. <p>
  195. <table nowrap border="0" cellspacing="0" cellpadding="2" width="100%">
  196. <tr><td bgcolor="#294563"><font color="#ffffff"><a name="Having Problems?"><strong>Having Problems?</strong></a></font></td></tr>
  197. </table>
  198. <p>
  199. This page details some steps you can take to try and resolve
  200. any problems you may be having with Ant. If you find you can't
  201. resolve the problem, then this page will help you collect some of
  202. the relevant information to provide in a bug report. This information
  203. will help the Ant developers understand and resolve the problem.
  204. Of course, not all the steps here will make sense for every problem
  205. you may encounter - these are just some suggestions to point
  206. you in the right direction.
  207. </p>
  208. <p>
  209. <a name="Read the Manual"><h4>Read the Manual</h4></a>
  210. <p>
  211. The first step to take when you have a problem with Ant is to read
  212. the <a href="manual/index.html">manual</a> entry for the task or
  213. concept that is giving you trouble. In particular, check the
  214. meaning of a task's attributes and nested elements. Perhaps an
  215. attribute is available that would provide the behavior you require.
  216. If you have problems with the manual itself, you can submit a
  217. documentation bug report (see below) to help us improve the Ant
  218. documentation.
  219. </p>
  220. </p>
  221. <p>
  222. <a name="Examine Debug Output"><h4>Examine Debug Output</h4></a>
  223. <p>
  224. If you're still having a problem, the next step is to try and
  225. gather additional information about what Ant is doing.
  226. Try running Ant with the <code>verbose</code> flag:
  227. <br /><br />
  228. <font face="verdana" size="-1">ant -verbose</font>
  229. <br /><br />
  230. or
  231. <br /><br />
  232. <font face="verdana" size="-1">ant -v</font>
  233. <br /><br />
  234. This will produce output that starts like the following:</p>
  235. <table>
  236. <tr>
  237. <td bgcolor="#a0ddf0" colspan="" rowspan=""
  238. valign="top" align="left">
  239. <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  240. Ant version 1.4.1 compiled on October 11 2001<br />
  241. Buildfile: build.xml<br />
  242. Detected Java version: 1.3 in: D:\usr\local\java\jdk13\jre<br />
  243. Detected OS: Windows NT<br />
  244. parsing buildfile D:\ant\build.xml
  245. with URI = file:D:/ant/build.xml<br />
  246. Project base dir set to: D:\ant<br />
  247. [property] Loading Environment env.<br />
  248. [property] Loading D:\ant\conf.properties<br />
  249. Build sequence for target 'debug' is [debug]<br />
  250. Complete build sequence is [debug, gensrc, compile, jar, test]<br />
  251. . . .<br />
  252. </font>
  253. </td>
  254. </tr>
  255. </table>
  256. <p>
  257. You should be able to see from the trace more about what Ant
  258. is doing and why it's taking a particular course of action.
  259. If you need even more information, you can use the
  260. <nobr><code>-debug</code></nobr> flag rather than
  261. <nobr><code>-verbose</code></nobr>.
  262. This will generally produce so much
  263. output that you may want to save the output to a file and
  264. analyze it in an editor. You can save the output using the
  265. <nobr><code>-logfile &lt;filename&gt;</code></nobr> flag, or
  266. using redirection.
  267. </p>
  268. <p>
  269. Once you have all this debug information, how can you use it
  270. to solve your problem? That will depend on the task in question
  271. and the nature of your problem. Each task logs different aspects
  272. of its operation, but it should give you an idea of what is going
  273. on. For example, the <code>&lt;javac&gt;</code> task logs the
  274. reasons why it
  275. chooses to compile particular class files and not others, along
  276. with which compiler it is using and the arguments it will pass
  277. to that compiler. The following partial trace shows why
  278. <code>&lt;javac&gt;</code> is adding one class file but
  279. skipping another.
  280. This is followed by which compiler it will be using, the
  281. arguments that will get passed to the compiler,
  282. and a list of all the class files to be compiled.
  283. </p>
  284. <table>
  285. <tr>
  286. <td bgcolor="#a0ddf0" colspan="" rowspan=""
  287. valign="top" align="left">
  288. <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  289. [javac] Test.java omitted as D:\classes\Test.class is up to date.<br />
  290. [javac] Unset.java added as D:\classes\Unset.class is outdated.<br />
  291. [javac] Compiling 1 source file to D:\classes<br />
  292. [javac] Using classic compiler<br />
  293. [javac] Compilation args: -d D:\classes -classpath D:\classes;<br />
  294. D:\jdk118\classes.zip; -sourcepath D:\src\java -g:none<br />
  295. [javac] File to be compiled:<br />
  296. D:\src\java\Unset.java<br />
  297. </font>
  298. </td>
  299. </tr>
  300. </table>
  301. <p>
  302. In many cases, Ant tasks are wrappers around OS commands or
  303. other Java classes. In debug mode, many of these tasks will
  304. print out the equivalent command line, as the
  305. <code>&lt;javac&gt;</code> task
  306. output does. If you are having a problem, it is often useful to
  307. run the command directly from the command line, in the same way
  308. Ant is running it, and see if the problem occurs from there
  309. as well. The problem may be in the command that is being run,
  310. or it may be in the way the Ant task is running the command.
  311. You can also see the effect of changing attribute values on the
  312. generated command line. This can help you to understand whether
  313. you are using the correct attributes and values.
  314. </p>
  315. </p>
  316. <p>
  317. <a name="Has It Been Fixed?"><h4>Has It Been Fixed?</h4></a>
  318. <p>
  319. After examining the debug output, if you still believe that the
  320. problem you are having is caused by Ant, chances are that someone
  321. else may have already encountered this problem, and perhaps it has
  322. been fixed. The next step, therefore, may be to try a nightly build
  323. of Ant to see if the problem has been fixed. Nightly builds for Ant
  324. are available from the
  325. <a href="http://cvs.apache.org/builds/jakarta-ant/nightly/">
  326. Jakarta web site</a>. While Ant nightly builds are typically quite
  327. stable and are used by
  328. <a href="http://cvs.apache.org/builds/gump/latest/">Gump</a>
  329. to build many other Jakarta projects, these builds should
  330. nonetheless be treated as experimental. Note that nightly builds
  331. do not build many of the optional tasks the come with Ant.
  332. A snapshot of these optional tasks is occasionally uploaded to
  333. the nightly download
  334. <a href="http://cvs.apache.org/builds/jakarta-ant/nightly/optional/">
  335. area</a>. However, even this snapshot does not contain every
  336. optional task.
  337. </p>
  338. </p>
  339. <p>
  340. <a name="Has It Been Reported?"><h4>Has It Been Reported?</h4></a>
  341. <p>
  342. If the current nightly build doesn't resolve your problem, it is
  343. possible that someone else has reported the issue. It is time to
  344. look at the <a href="http://nagoya.apache.org/bugzilla/">
  345. Apache Bug Database</a>. This system is easy to use, and it will
  346. let you search the <a href="http://nagoya.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;email1=&amp;emailtype1=substring&amp;emailassigned_to1=1&amp;email2=&amp;emailtype2=substring&amp;emailreporter2=1&amp;bugidtype=include&amp;bug_id=&amp;changedin=&amp;votes=&amp;chfieldfrom=&amp;chfieldto=Now&amp;chfieldvalue=&amp;product=Ant&amp;short_desc=&amp;short_desc_type=substring&amp;long_desc=&amp;long_desc_type=substring&amp;bug_file_loc=&amp;bug_file_loc_type=substring&amp;keywords=&amp;keywords_type=anywords&amp;field0-0-0=noop&amp;type0-0-0=noop&amp;value0-0-0=&amp;order=bugs.bug_id">
  347. currently open</a> and resolved bugs to see if your problem has
  348. already been reported. If your problem has been reported, you can
  349. see whether any of the developers have commented, suggesting
  350. workarounds, or the reason for the bug, etc. Or you may have
  351. information to add (see about creating and modifying bug reports
  352. below), in which case, go right ahead and add the information.
  353. If you don't have any additional information, you may just want
  354. to vote for this bug, and perhaps
  355. add yourself to the <code>CC</code> list to follow the progress
  356. of this bug.
  357. </p>
  358. </p>
  359. <p>
  360. <a name="Filing a Bug Report"><h4>Filing a Bug Report</h4></a>
  361. <p>
  362. By this time, you may have decided that there is an unreported
  363. bug in Ant. You have a few choices at this point. You can send
  364. an email to the <nobr><code>ant-user</code></nobr> mailing list
  365. to see if
  366. others have encountered your issue and find out how they may
  367. have worked around it. If after some discussion, you feel it
  368. is time to create
  369. a bug report, this is a simple operation in the bug database.
  370. Please try to provide as much information as possible in order
  371. to assist the developers in resolving the bug. Please try to enter
  372. correct values for the various inputs when creating the bug, such
  373. as which version of Ant you are running, and on which platform,
  374. etc. Once the bug is created, you can also add attachments to
  375. the bug report.
  376. </p>
  377. <p>
  378. What information should you include in your bug report? The
  379. easiest bugs to fix are those that are most easily reproducible,
  380. so it is really helpful if you can produce a small test case that
  381. exhibits the problem. In this case, you would attach the build file
  382. and any other files necessary to reproduce the problem, probably
  383. packed together in an archive. If you can't produce a test case,
  384. you should try to include a snippet from your build file and the
  385. relevant sections from the verbose or debug output from Ant. Try
  386. to include the header information where Ant states the version,
  387. the OS and VM information, etc. As debug output is likely to be
  388. very large, it's best to remove any output that is not
  389. relevant. Once the bug is entered into the bug database, you
  390. will be kept informed by email about progress on the bug. If
  391. you receive email asking for further information, please try to
  392. respond, as it will aid in the resolution of your bug.
  393. </p>
  394. </p>
  395. <p>
  396. <a name="Asking for an Enhancement"><h4>Asking for an Enhancement</h4></a>
  397. <p>
  398. Sometimes, you may find that Ant just doesn't do what you need it
  399. to. It isn't a bug, as such, since Ant is working the way it is
  400. supposed to work. Perhaps it is some additional functionality for
  401. a task that hasn't been thought of yet, or maybe a completely new
  402. task. For these situations, you will
  403. want to raise an <i>enhancement request</i>. Enhancement requests
  404. are managed using the same Apache Bug Database described above.
  405. These are just a different type of bug report. If you look in the
  406. bug database, you will see that one of the severity settings for
  407. a bug is "Enhancement". Just fill the bug report in,
  408. set the severity of the bug to "Enhancement", and
  409. state in the description how you would like to have Ant enhanced.
  410. Again, you should first check whether there are any existing
  411. enhancment requests that cover your needs. If so, just add your
  412. vote to these.
  413. </p>
  414. </p>
  415. <p>
  416. <a name="Fixing the Bug"><h4>Fixing the Bug</h4></a>
  417. <p>
  418. If you aren't satisfied with just filing a bug report, you can
  419. try to find the cause of the problem and provide a fix yourself.
  420. The best way to do that is by working with the latest code from CVS.
  421. Alternatively, you can work with the source code available from the
  422. <a href="http://jakarta.apache.org/builds/jakarta-ant/release/v1.4.1/src/">
  423. source distributions</a>. If you
  424. are going to tackle the problem at this level, you may want to
  425. discuss some details first on the <nobr><code>ant-dev</code></nobr>
  426. mailing list. Once you have a fix for the problem, you may submit
  427. the fix as a <i>patch</i> to either the
  428. <nobr><code>ant-dev</code></nobr> mailing
  429. list, or enter the bug database as described above and attach the
  430. patch to the bug report. Using the bug database has the advantage
  431. of being able to track the progress of your patch.
  432. </p>
  433. <p>
  434. If you have a patch to submit and are sending it to the
  435. <nobr><code>ant-dev</code></nobr> mailing list,
  436. prefix "[PATCH]"
  437. to your message subject. Please include any relevant bug numbers.
  438. Patch files should be created with the <nobr><code>-u</code></nobr>
  439. option of the
  440. <code>diff</code> or <code>cvs diff</code> command. For
  441. example:<br /><br />
  442. <font face="verdana" size="-1">
  443. diff -u Javac.java.orig Javac.java &gt; javac.diffs<br /><br />
  444. </font>
  445. or, if you have source from CVS:<br /><br />
  446. <font face="verdana" size="-1">
  447. cvs diff -u Javac.java &gt; javac.diffs<br /><br />
  448. </font>
  449. Note: You should give your patch files meaningful names.
  450. This makes it easier for developers who need to apply a number
  451. of different patch files.
  452. </p>
  453. </p>
  454. </p>
  455. </div>
  456. </td><td width="10"><img width="10" height="1" alt="" src="images/spacer.gif"></td>
  457. </tr>
  458. </table>
  459. </td>
  460. </tr>
  461. </table>
  462. <table summary="footer" cellspacing="0" cellpadding="0" width="100%" height="20" border="0">
  463. <tr>
  464. <td colspan="2" height="1" bgcolor="#4C6C8F"><img height="1" width="1" alt="" src="images/spacer.gif"><a href="images/label.gif"></a><a href="images/page.gif"></a><a href="images/chapter.gif"></a><a href="images/chapter_open.gif"></a><a href="images/current.gif"></a><a href="/favicon.ico"></a></td>
  465. </tr>
  466. <tr>
  467. <td colspan="2" bgcolor="#CFDCED" class="copyright" align="center"><font size="2" face="Arial, Helvetica, Sans-Serif">Copyright &copy;
  468. 2002&nbsp;The Apache Software Foundation. All rights reserved.<script type="text/javascript" language="JavaScript"><!--
  469. document.write(" - "+"Last Published: " + document.lastModified);
  470. // --></script></font></td>
  471. </tr>
  472. </table>
  473. </body>
  474. </html>