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 25 KiB

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