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.

faq.html 88 kB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192939495969798991001011021031041051061071081091101111121131141151161171181191201211221231241251261271281291301311321331341351361371381391401411421431441451461471481491501511521531541551561571581591601611621631641651661671681691701711721731741751761771781791801811821831841851861871881891901911921931941951961971981992002012022032042052062072082092102112122132142152162172182192202212222232242252262272282292302312322332342352362372382392402412422432442452462472482492502512522532542552562572582592602612622632642652662672682692702712722732742752762772782792802812822832842852862872882892902912922932942952962972982993003013023033043053063073083093103113123133143153163173183193203213223233243253263273283293303313323333343353363373383393403413423433443453463473483493503513523533543553563573583593603613623633643653663673683693703713723733743753763773783793803813823833843853863873883893903913923933943953963973983994004014024034044054064074084094104114124134144154164174184194204214224234244254264274284294304314324334344354364374384394404414424434444454464474484494504514524534544554564574584594604614624634644654664674684694704714724734744754764774784794804814824834844854864874884894904914924934944954964974984995005015025035045055065075085095105115125135145155165175185195205215225235245255265275285295305315325335345355365375385395405415425435445455465475485495505515525535545555565575585595605615625635645655665675685695705715725735745755765775785795805815825835845855865875885895905915925935945955965975985996006016026036046056066076086096106116126136146156166176186196206216226236246256266276286296306316326336346356366376386396406416426436446456466476486496506516526536546556566576586596606616626636646656666676686696706716726736746756766776786796806816826836846856866876886896906916926936946956966976986997007017027037047057067077087097107117127137147157167177187197207217227237247257267277287297307317327337347357367377387397407417427437447457467477487497507517527537547557567577587597607617627637647657667677687697707717727737747757767777787797807817827837847857867877887897907917927937947957967977987998008018028038048058068078088098108118128138148158168178188198208218228238248258268278288298308318328338348358368378388398408418428438448458468478488498508518528538548558568578588598608618628638648658668678688698708718728738748758768778788798808818828838848858868878888898908918928938948958968978988999009019029039049059069079089099109119129139149159169179189199209219229239249259269279289299309319329339349359369379389399409419429439449459469479489499509519529539549559569579589599609619629639649659669679689699709719729739749759769779789799809819829839849859869879889899909919929939949959969979989991000100110021003100410051006100710081009101010111012101310141015101610171018101910201021102210231024102510261027102810291030103110321033103410351036103710381039104010411042104310441045104610471048104910501051105210531054105510561057105810591060106110621063106410651066106710681069107010711072107310741075107610771078107910801081108210831084108510861087108810891090109110921093109410951096109710981099110011011102110311041105110611071108110911101111111211131114111511161117111811191120112111221123112411251126112711281129113011311132113311341135113611371138113911401141114211431144114511461147114811491150115111521153115411551156115711581159116011611162116311641165116611671168116911701171117211731174117511761177117811791180118111821183118411851186118711881189119011911192119311941195119611971198119912001201120212031204120512061207120812091210121112121213121412151216121712181219122012211222122312241225122612271228122912301231123212331234123512361237123812391240124112421243124412451246124712481249125012511252125312541255125612571258125912601261126212631264126512661267126812691270127112721273127412751276127712781279128012811282128312841285128612871288128912901291129212931294129512961297129812991300130113021303130413051306130713081309131013111312131313141315131613171318131913201321132213231324132513261327132813291330133113321333133413351336133713381339134013411342134313441345134613471348134913501351135213531354135513561357135813591360136113621363136413651366136713681369137013711372137313741375137613771378137913801381138213831384138513861387138813891390139113921393139413951396139713981399140014011402140314041405140614071408140914101411141214131414141514161417141814191420142114221423142414251426142714281429143014311432143314341435143614371438143914401441144214431444144514461447144814491450145114521453145414551456145714581459146014611462146314641465146614671468146914701471147214731474147514761477147814791480148114821483148414851486148714881489149014911492149314941495149614971498149915001501150215031504150515061507150815091510151115121513151415151516151715181519152015211522152315241525152615271528152915301531153215331534153515361537153815391540154115421543154415451546154715481549155015511552155315541555155615571558155915601561156215631564156515661567156815691570157115721573157415751576157715781579158015811582158315841585158615871588158915901591159215931594159515961597159815991600160116021603160416051606160716081609161016111612161316141615161616171618161916201621162216231624162516261627162816291630163116321633163416351636163716381639164016411642164316441645164616471648164916501651165216531654165516561657165816591660166116621663166416651666166716681669167016711672167316741675167616771678167916801681168216831684168516861687168816891690169116921693169416951696169716981699170017011702170317041705170617071708170917101711171217131714171517161717171817191720172117221723172417251726172717281729173017311732173317341735173617371738173917401741174217431744174517461747174817491750175117521753175417551756175717581759176017611762176317641765176617671768176917701771177217731774177517761777177817791780178117821783178417851786178717881789179017911792179317941795179617971798179918001801180218031804180518061807180818091810181118121813181418151816181718181819182018211822182318241825182618271828182918301831183218331834183518361837183818391840184118421843184418451846184718481849185018511852185318541855185618571858185918601861186218631864186518661867186818691870187118721873187418751876187718781879188018811882188318841885188618871888188918901891189218931894189518961897189818991900190119021903190419051906190719081909191019111912191319141915191619171918191919201921192219231924192519261927192819291930193119321933193419351936193719381939194019411942194319441945194619471948194919501951195219531954195519561957195819591960196119621963196419651966196719681969197019711972197319741975197619771978197919801981198219831984
  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 - Frequently Asked Questions</title>
  7. <link type="text/css" href="./page.css" rel="stylesheet">
  8. <meta name="author" content="Stefan Bodewig">
  9. <meta name="email" content="bodewig@apache.org">
  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 align="center">
  72. <a href="http://ApacheCon.Com/"><img width="135" height="50"
  73. border="0" style="background-color: white"
  74. src="http://apache.org/images/ac2005eu_135x50.gif"
  75. alt="ApacheCon!" title="Come to ApacheCon!"/></a>
  76. </div>
  77. <div class="menu">
  78. <ul>
  79. <li class="menuheader">Apache Ant
  80. <ul>
  81. <li>
  82. <a href="./index.html">Welcome</a>
  83. </li>
  84. <li>
  85. <a href="./license.html">License</a>
  86. </li>
  87. <li>
  88. <a href="./antnews.html">News</a>
  89. </li>
  90. </ul>
  91. </li>
  92. <li class="menuheader">Documentation
  93. <ul>
  94. <li>
  95. <a href="./manual/index.html">Manual</a>
  96. </li>
  97. <li>
  98. <a href="./projects.html">Related Projects</a>
  99. </li>
  100. <li>
  101. <a href="./external.html">External Tools and Tasks</a>
  102. </li>
  103. <li>
  104. <a href="./resources.html">Resources</a>
  105. </li>
  106. <li>
  107. <span class="sel">Frequently Asked Questions</span>
  108. </li>
  109. <li>
  110. <a href="http://wiki.apache.org/ant/FrontPage">Wiki</a>
  111. </li>
  112. <li>
  113. <a href="./problems.html">Having Problems?</a>
  114. </li>
  115. </ul>
  116. </li>
  117. <li class="menuheader">Download
  118. <ul>
  119. <li>
  120. <a href="http://ant.apache.org/bindownload.cgi">Binary Distributions</a>
  121. </li>
  122. <li>
  123. <a href="http://ant.apache.org/srcdownload.cgi">Source Distributions</a>
  124. </li>
  125. </ul>
  126. </li>
  127. <li class="menuheader">Contributing
  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://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant">Bug Database</a>
  137. </li>
  138. <li>
  139. <a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant&amp;bug_severity=enhancement">Enhancement Requests</a>
  140. </li>
  141. <li>
  142. <a href="http://www.apache.org/foundation/contributing.html">Donations</a>
  143. </li>
  144. </ul>
  145. </li>
  146. <li class="menuheader">Project Management
  147. <ul>
  148. <li>
  149. <a href="./contributors.html">Contributors</a>
  150. </li>
  151. <li>
  152. <a href="./mission.html">Apache Ant Mission</a>
  153. </li>
  154. <li>
  155. <a href="./bylaws.html">Project Bylaws</a>
  156. </li>
  157. <li>
  158. <a href="./legal.html">Legal</a>
  159. </li>
  160. </ul>
  161. </li>
  162. </ul>
  163. </div>
  164. <img style="float: left" height="10" width="10" border="0" alt="" src="./images/menu-left.gif">
  165. <img style="float: right" height="10" width="10" border="0" alt="" src="./images/menu-right.gif">
  166. </div>
  167. <div class="lightbluebar">&nbsp;</div>
  168. <div class="main">
  169. <div class="content">
  170. <h1 class="title">Frequently Asked Questions</h1>
  171. <h3 class="section">Questions</h3>
  172. <h4 class="toc">About this FAQ</h4>
  173. <ul>
  174. <li><a href="#latest-version">
  175. Where do I find the latest version of this
  176. document?
  177. </a></li>
  178. <li><a href="#adding-faqs">
  179. How can I contribute to this FAQ?
  180. </a></li>
  181. <li><a href="#creating-faq">
  182. How do you create the HTML version of this
  183. FAQ?
  184. </a></li>
  185. </ul>
  186. <h4 class="toc">General</h4>
  187. <ul>
  188. <li><a href="#what-is-ant">
  189. What is Apache Ant?
  190. </a></li>
  191. <li><a href="#ant-name">
  192. Why do you call it Ant?
  193. </a></li>
  194. <li><a href="#history">
  195. Tell us a little bit about Ant's history.
  196. </a></li>
  197. </ul>
  198. <h4 class="toc">Installation</h4>
  199. <ul>
  200. <li><a href="#no-gnu-tar">
  201. I get checksum errors when I try to extract the
  202. <code>tar.gz</code> distribution file. Why?
  203. </a></li>
  204. <li><a href="#RedHat_ES_3">
  205. How do you get ant-1.6.x (or any version later than
  206. 1.5.2) to work on on RedHat ES 3?
  207. </a></li>
  208. </ul>
  209. <h4 class="toc">How do I ...</h4>
  210. <ul>
  211. <li><a href="#implement-os-specific-configuration">
  212. How do I realize os--specific configurations?
  213. </a></li>
  214. <li><a href="#adding-external-tasks">
  215. How do I add an external task that I've written to the
  216. page "External Tools and Tasks"?
  217. </a></li>
  218. <li><a href="#create-extensions">
  219. How do I create new tasks?
  220. </a></li>
  221. <li><a href="#passing-cli-args">
  222. How do I pass parameters from the command line to my
  223. build file?
  224. </a></li>
  225. <li><a href="#jikes-switches">
  226. How can I use Jikes-specific command-line
  227. switches?
  228. </a></li>
  229. <li><a href="#shell-redirect-1">
  230. How do I include a &lt; character in my command-line arguments?
  231. </a></li>
  232. <li><a href="#shell-redirect-2">
  233. How do I redirect standard input or standard output
  234. in the <code>&lt;exec&gt;</code> task?
  235. </a></li>
  236. <li><a href="#batch-shell-execute">
  237. How do I execute a batch file or shell script from Ant?
  238. </a></li>
  239. <li><a href="#multi-conditions">
  240. I want to execute a particular target only if
  241. multiple conditions are true.
  242. </a></li>
  243. <li><a href="#encoding">
  244. How can I include national characters like German
  245. umlauts in my build file?
  246. </a></li>
  247. <li><a href="#use-zip-instead-of-jar">
  248. How do I use <code>jar</code>'s <code>M</code> switch?
  249. I don't want a MANIFEST.
  250. </a></li>
  251. <li><a href="#propertyvalue-as-name-for-property">
  252. How can I do something like <code>&lt;property name="prop"
  253. value="${${anotherprop}}"/&gt;</code> (double expanding the property)?
  254. </a></li>
  255. </ul>
  256. <h4 class="toc">It doesn't work (as expected)</h4>
  257. <ul>
  258. <li><a href="#genral-advice">
  259. General Advice
  260. </a></li>
  261. <li><a href="#always-recompiles">
  262. Why does Ant always recompile all my Java files?
  263. </a></li>
  264. <li><a href="#defaultexcludes">
  265. I've used a <code>&lt;delete&gt;</code> task to
  266. delete unwanted SourceSafe control files (CVS files, editor
  267. backup files, etc.), but it doesn't seem to work; the files
  268. never get deleted. What's wrong?
  269. </a></li>
  270. <li><a href="#stop-dependency">
  271. I have a target I want to skip if a property is set,
  272. so I have <code>unless="property"</code> as an attribute
  273. of the target, but all the targets this target
  274. depends on are still executed. Why?
  275. </a></li>
  276. <li><a href="#include-order">
  277. In my <code>&lt;fileset&gt;</code>, I've put in an
  278. <code>&lt;exclude&gt;</code> of all files followed by an
  279. <code>&lt;include&gt;</code> of just the files I want, but it
  280. isn't giving me any files at all. What's wrong?
  281. </a></li>
  282. <li><a href="#properties-not-trimmed">
  283. <code>ant</code> failed to build my program via javac
  284. even when I put the needed jars in an external
  285. <code>build.properties</code> file and reference them by
  286. <code>pathelement</code> or <code>classpath refid</code>.
  287. </a></li>
  288. <li><a href="#winzip-lies">
  289. Ant creates WAR files with a lower-case
  290. <code>web-inf</code> or JAR files with a lower-case
  291. <code>meta-inf</code> directory.
  292. </a></li>
  293. <li><a href="#NoClassDefFoundError">
  294. I installed Ant 1.6.x and now get
  295. <code>Exception in thread "main" java.lang.NoClassDefFoundError:
  296. </code>
  297. </a></li>
  298. <li><a href="#InstantiationException">
  299. I installed Ant 1.6.x and now get
  300. <code>java.lang.InstantiationException: org.apache.tools.ant.Main</code>
  301. </a></li>
  302. <li><a href="#mangled-manifest">
  303. Whenever I use the Ant jar or manifest related tasks, long lines in
  304. my manifest are wrapped at 70 characters and the resulting jar does
  305. not work in my application server. Why does Ant do this?
  306. </a></li>
  307. </ul>
  308. <h4 class="toc">Ant and IDEs/Editors</h4>
  309. <ul>
  310. <li><a href="#integration">
  311. Is Ant supported by my IDE/Editor?
  312. </a></li>
  313. <li><a href="#emacs-mode">
  314. Why doesn't (X)Emacs/vi/MacOS X's project builder
  315. correctly parse the error messages generated by Ant?
  316. </a></li>
  317. </ul>
  318. <h4 class="toc">Advanced Issues</h4>
  319. <ul>
  320. <li><a href="#dtd">
  321. Is there a DTD that I can use to validate my build
  322. files?
  323. </a></li>
  324. <li><a href="#xml-entity-include">
  325. How do I include an XML snippet in my build file?
  326. </a></li>
  327. <li><a href="#mail-logger">
  328. How do I send an email with the result of my build
  329. process?
  330. </a></li>
  331. <li><a href="#listener-properties">
  332. How do I get at the properties that Ant was running
  333. with from inside BuildListener?
  334. </a></li>
  335. </ul>
  336. <h4 class="toc">Known Problems</h4>
  337. <ul>
  338. <li><a href="#remove-cr">
  339. &lt;chmod&gt; or &lt;exec&gt; doesn't work in Ant
  340. 1.3 on Unix
  341. </a></li>
  342. <li><a href="#javadoc-cannot-execute">
  343. JavaDoc failed: java.io.IOException: javadoc: cannot execute
  344. </a></li>
  345. <li><a href="#delegating-classloader">
  346. &lt;style&gt; or &lt;junit&gt; ignores my
  347. &lt;classpath&gt;
  348. </a></li>
  349. <li><a href="#delegating-classloader-1.5">
  350. &lt;style&gt; or &lt;junit&gt; ignores my
  351. &lt;classpath&gt; - Ant 1.5.x version
  352. </a></li>
  353. <li><a href="#delegating-classloader-1.6">
  354. &lt;style&gt; or &lt;junit&gt; ignores my
  355. &lt;classpath&gt; - Ant 1.6.x version
  356. </a></li>
  357. <li><a href="#winxp-jdk14-ant14">
  358. When running Ant 1.4 on Windows XP and JDK 1.4, I get
  359. various errors when trying to <code>&lt;exec&gt;</code>, fork
  360. <code>&lt;java&gt;</code> or access environment
  361. variables.
  362. </a></li>
  363. <li><a href="#1.5-cygwin-sh">
  364. The <code>ant</code> wrapper script of Ant 1.5 fails
  365. for Cygwin if <code>ANT_HOME</code> is set to a Windows style
  366. path.
  367. </a></li>
  368. <li><a href="#1.5.2-zip-broken">
  369. <code>&lt;zip&gt;</code> is broken in Ant 1.5.2.
  370. </a></li>
  371. <li><a href="#unknownelement.taskcontainer">
  372. Why do my custom task containers see Unknown Elements in Ant 1.6
  373. - they worked in Ant 1.5?
  374. </a></li>
  375. <li><a href="#java.exception.stacktrace">
  376. The program I run via &lt;java&gt; throws an exception but I
  377. can't seem to get the full stack trace.
  378. </a></li>
  379. <li><a href="#junit-no-runtime-xml">
  380. Using format="xml", &lt;junit&gt; fails with a
  381. <code>NoClassDefFoundError</code> if forked.
  382. </a></li>
  383. <li><a href="#xalan-jdk1.5">
  384. <code>&lt;junitreport&gt;</code> doesn't work with JDK 1.5 but
  385. worked fine with JDK 1.4.
  386. </a></li>
  387. </ul>
  388. <h3 class="section">Answers</h3>
  389. <p class="faq">
  390. <a name="latest-version"></a>
  391. Where do I find the latest version of this
  392. document?
  393. </p>
  394. <p>The latest version can always be found at Ant's homepage
  395. <a href="http://ant.apache.org/faq.html">http://ant.apache.org/faq.html</a>.</p>
  396. <p class="faq">
  397. <a name="adding-faqs"></a>
  398. How can I contribute to this FAQ?
  399. </p>
  400. <p>The page you are looking it is generated from
  401. <a href="http://cvs.apache.org/viewcvs.cgi/~checkout~/ant/xdocs/faq.xml">this</a>
  402. document. If you want to add a new question, please submit
  403. a patch against this document to one of Ant's mailing lists;
  404. hopefully, the structure is self-explanatory.</p>
  405. <p>If you don't know how to create a patch, see the patches
  406. section of <a href="http://jakarta.apache.org/site/source.html">this
  407. page</a>.</p>
  408. <p class="faq">
  409. <a name="creating-faq"></a>
  410. How do you create the HTML version of this
  411. FAQ?
  412. </p>
  413. <p>We use
  414. <a href="http://jakarta.apache.org/velocity/anakia.html">Anakia</a>
  415. to render the HTML version from the original XML file.</p>
  416. <p>The Velocity stylesheets used to process the XML files can
  417. be found in the <code>xdocs/stylesheets</code> subdirectory of
  418. Ant's CVS repository - the build file
  419. <code>docs.xml</code> at the top level of the ant CVS
  420. module is used to drive Anakia.</p>
  421. <p>This file assumes that you have the
  422. <code>jakarta-site2</code> CVS module checked out as well, but
  423. if you follow the instruction from Anakia's homepage, you
  424. should get it to work without that. Just make sure all
  425. required jars are in the task's classpath.</p>
  426. <p class="faq">
  427. <a name="what-is-ant"></a>
  428. What is Apache Ant?
  429. </p>
  430. <p> Ant is a Java-based build tool. In theory, it is kind of
  431. like Make, without Make's wrinkles and with the full
  432. portability of pure Java code.</p>
  433. <p class="faq">
  434. <a name="ant-name"></a>
  435. Why do you call it Ant?
  436. </p>
  437. <p>According to Ant's original author, James Duncan
  438. Davidson, the name is an acronym for "Another Neat
  439. Tool".</p>
  440. <p>Later explanations go along the lines of "ants
  441. do an extremely good job at building things", or
  442. "ants are very small and can carry a weight dozens of times
  443. their own" - describing what Ant is intended to
  444. be.</p>
  445. <p class="faq">
  446. <a name="history"></a>
  447. Tell us a little bit about Ant's history.
  448. </p>
  449. <p>Initially, Ant was part of the Tomcat code base, when it was
  450. donated to the Apache Software Foundation. It was
  451. created by James Duncan Davidson, who is also the original
  452. author of Tomcat. Ant was there to build Tomcat, nothing
  453. else.</p>
  454. <p>Soon thereafter, several open source Java projects realized
  455. that Ant could solve the problems they had with Makefiles.
  456. Starting with the projects hosted at Jakarta and the old Java
  457. Apache project, Ant spread like a virus and is now the build
  458. tool of choice for a lot of projects.</p>
  459. <p>In January 2000, Ant was moved to a separate CVS module and
  460. was promoted to a project of its own, independent of
  461. Tomcat, and became Apache Ant.</p>
  462. <p>The first version of Ant that was exposed to a larger audience
  463. was the one that shipped with Tomcat's 3.1 release on 19 April
  464. 2000. This version has later been referred to as Ant
  465. 0.3.1.</p>
  466. <p>The first official release of Ant as a stand-alone product was
  467. Ant 1.1, released on 19 July 2000. The complete release
  468. history:</p>
  469. <table class="ForrestTable" cellspacing="1" cellpadding="4">
  470. <tr>
  471. <th colspan="1" rowspan="1"
  472. valign="top" align="left">
  473. Ant Version
  474. </th>
  475. <th colspan="1" rowspan="1"
  476. valign="top" align="left">
  477. Release Date
  478. </th>
  479. </tr>
  480. <tr>
  481. <td colspan="1" rowspan="1"
  482. valign="top" align="left">
  483. 1.1
  484. </td>
  485. <td colspan="1" rowspan="1"
  486. valign="top" align="left">
  487. 19 July 2000
  488. </td>
  489. </tr>
  490. <tr>
  491. <td colspan="1" rowspan="1"
  492. valign="top" align="left">
  493. 1.2
  494. </td>
  495. <td colspan="1" rowspan="1"
  496. valign="top" align="left">
  497. 24 October 2000
  498. </td>
  499. </tr>
  500. <tr>
  501. <td colspan="1" rowspan="1"
  502. valign="top" align="left">
  503. 1.3
  504. </td>
  505. <td colspan="1" rowspan="1"
  506. valign="top" align="left">
  507. 3 March 2001
  508. </td>
  509. </tr>
  510. <tr>
  511. <td colspan="1" rowspan="1"
  512. valign="top" align="left">
  513. 1.4
  514. </td>
  515. <td colspan="1" rowspan="1"
  516. valign="top" align="left">
  517. 3 September 2001
  518. </td>
  519. </tr>
  520. <tr>
  521. <td colspan="1" rowspan="1"
  522. valign="top" align="left">
  523. 1.4.1
  524. </td>
  525. <td colspan="1" rowspan="1"
  526. valign="top" align="left">
  527. 11 October 2001
  528. </td>
  529. </tr>
  530. <tr>
  531. <td colspan="1" rowspan="1"
  532. valign="top" align="left">
  533. 1.5
  534. </td>
  535. <td colspan="1" rowspan="1"
  536. valign="top" align="left">
  537. 10 July 2002
  538. </td>
  539. </tr>
  540. <tr>
  541. <td colspan="1" rowspan="1"
  542. valign="top" align="left">
  543. 1.5.1
  544. </td>
  545. <td colspan="1" rowspan="1"
  546. valign="top" align="left">
  547. 3 October 2002
  548. </td>
  549. </tr>
  550. <tr>
  551. <td colspan="1" rowspan="1"
  552. valign="top" align="left">
  553. 1.5.2
  554. </td>
  555. <td colspan="1" rowspan="1"
  556. valign="top" align="left">
  557. 3 March 2003
  558. </td>
  559. </tr>
  560. <tr>
  561. <td colspan="1" rowspan="1"
  562. valign="top" align="left">
  563. 1.5.3
  564. </td>
  565. <td colspan="1" rowspan="1"
  566. valign="top" align="left">
  567. 9 April 2003
  568. </td>
  569. </tr>
  570. <tr>
  571. <td colspan="1" rowspan="1"
  572. valign="top" align="left">
  573. 1.5.4
  574. </td>
  575. <td colspan="1" rowspan="1"
  576. valign="top" align="left">
  577. 12 August 2003
  578. </td>
  579. </tr>
  580. <tr>
  581. <td colspan="1" rowspan="1"
  582. valign="top" align="left">
  583. 1.6.0
  584. </td>
  585. <td colspan="1" rowspan="1"
  586. valign="top" align="left">
  587. 18 December 2003
  588. </td>
  589. </tr>
  590. <tr>
  591. <td colspan="1" rowspan="1"
  592. valign="top" align="left">
  593. 1.6.1
  594. </td>
  595. <td colspan="1" rowspan="1"
  596. valign="top" align="left">
  597. 12 February 2004
  598. </td>
  599. </tr>
  600. <tr>
  601. <td colspan="1" rowspan="1"
  602. valign="top" align="left">
  603. 1.6.2
  604. </td>
  605. <td colspan="1" rowspan="1"
  606. valign="top" align="left">
  607. 16 July 2004
  608. </td>
  609. </tr>
  610. <tr>
  611. <td colspan="1" rowspan="1"
  612. valign="top" align="left">
  613. 1.6.3
  614. </td>
  615. <td colspan="1" rowspan="1"
  616. valign="top" align="left">
  617. 28 April 2005
  618. </td>
  619. </tr>
  620. </table>
  621. <p class="faq">
  622. <a name="no-gnu-tar"></a>
  623. I get checksum errors when I try to extract the
  624. <code>tar.gz</code> distribution file. Why?
  625. </p>
  626. <p>Ant's distribution contains file names that are longer
  627. than 100 characters, which is not supported by the standard
  628. tar file format. Several different implementations of tar use
  629. different and incompatible ways to work around this
  630. restriction.</p>
  631. <p>Ant's &lt;tar&gt; task can create tar archives that use
  632. the GNU tar extension, and this has been used when putting
  633. together the distribution. If you are using a different
  634. version of tar (for example, the one shipping with Solaris),
  635. you cannot use it to extract the archive.</p>
  636. <p>The solution is to either install GNU tar, which can be
  637. found <a href="http://www.gnu.org/software/tar/tar.html">here</a>,
  638. or use the zip archive instead (you can extract it using
  639. <code>jar xf</code>).</p>
  640. <p class="faq">
  641. <a name="RedHat_ES_3"></a>
  642. How do you get ant-1.6.x (or any version later than
  643. 1.5.2) to work on on RedHat ES 3?
  644. </p>
  645. <p>Redhat ES 3.0 comes installed with ant 1.5.2. Even if you
  646. have your PATH and ANT_HOME variables set correctly to a later
  647. version of ant, you will always be forced to use the
  648. preinstalled version.</p>
  649. <p>To use a later version of ant on this OS you could do the
  650. following:</p>
  651. <pre class="code">
  652. $ ant -version
  653. Apache Ant version 1.5.2-23 compiled on November 12 2003
  654. $ su -
  655. # rpm -e ant ant-libs
  656. # exit
  657. $ hash -r
  658. $ ant -version
  659. Apache Ant version 1.6.2 compiled on July 16 2004
  660. </pre>
  661. <p class="faq">
  662. <a name="implement-os-specific-configuration"></a>
  663. How do I realize os--specific configurations?
  664. </p>
  665. <p>The core idea is using property files which name accords to the
  666. os-name. Then simply use the build-in property <tt>os.name</tt>.</p>
  667. <p>For better use you should also provide a file with defaul values.
  668. But be careful with the correct os-names. For test simply &lt;echo&gt;
  669. the ${os.name} on all machines and you can be sure to use the right
  670. file names.</p>
  671. <pre class="code">
  672. &lt;property file=&quot;${os.name}.properties&quot;/&gt;
  673. &lt;property file=&quot;default.properties&quot;/&gt;
  674. </pre>
  675. <p class="faq">
  676. <a name="adding-external-tasks"></a>
  677. How do I add an external task that I've written to the
  678. page "External Tools and Tasks"?
  679. </p>
  680. <p>Join and post a message to the dev or user mailing
  681. list (one list is enough), including the following
  682. information:</p>
  683. <ul>
  684. <li>the name of the task/tool</li>
  685. <li>a short description of the task/tool</li>
  686. <li>a Compatibility: entry stating with which version(s) of
  687. Ant the tool/task is compatible to</li>
  688. <li>a URL: entry linking to the main page of the tool/task</li>
  689. <li>a Contact: entry containing the email address or the URL
  690. of a webpage for the person or list to contact for issues
  691. related to the tool/task. <strong>Note that we'll add a
  692. link on the page, so any email address added there is not
  693. obfuscated and can (and probably will) be abused by robots
  694. harvesting websites for addresses to spam.</strong></li>
  695. <li>a License: entry containing the type of license for the
  696. tool/task</li>
  697. </ul>
  698. <p>The preferred format for this information is a patch to <a href="http://cvs.apache.org/viewcvs.cgi/~checkout~/ant/xdocs/external.xml">this</a>
  699. document.</p>
  700. <p>If you have written something bigger than a 'simple plugin' to Ant it
  701. may be better to add the link to <a href="projects.html">projects.html</a>.
  702. The procedure to add it is the same. The file to patch is <a href="http://cvs.apache.org/viewcvs.cgi/~checkout~/ant/xdocs/projects.xml">this</a>
  703. document. The syntax of that file is the same.</p>
  704. <p class="faq">
  705. <a name="create-extensions"></a>
  706. How do I create new tasks?
  707. </p>
  708. <p>Apart from a lot of information on using Ant, the
  709. <a href="manual/index.html">Manual</a> also contains information
  710. on how to extend Ant with new tasks. This information
  711. can be found under "Developing with Ant".</p>
  712. <p>Chances are that someone else already created the task you
  713. want to create, it may be wise to see
  714. <a href="external.html">External Tools and Tasks</a> and
  715. <a href="projects.html">Related Projects</a> first.</p>
  716. <p class="faq">
  717. <a name="passing-cli-args"></a>
  718. How do I pass parameters from the command line to my
  719. build file?
  720. </p>
  721. <p>Use properties. Using <code>ant
  722. -D<em>name</em>=<em>value</em></code> lets you define values for
  723. properties on the Ant command line. These properties can then be
  724. used within your build file as
  725. any normal property: <code>${<em>name</em>}</code> will put in
  726. <code><em>value</em></code>.</p>
  727. <p class="faq">
  728. <a name="jikes-switches"></a>
  729. How can I use Jikes-specific command-line
  730. switches?
  731. </p>
  732. <p>A couple of switches are supported via "magic"
  733. properties:</p>
  734. <table class="ForrestTable" cellspacing="1" cellpadding="4">
  735. <tr>
  736. <th colspan="1" rowspan="1"
  737. valign="top" align="left">
  738. switch
  739. </th>
  740. <th colspan="1" rowspan="1"
  741. valign="top" align="left">
  742. property
  743. </th>
  744. <th colspan="1" rowspan="1"
  745. valign="top" align="left">
  746. default
  747. </th>
  748. </tr>
  749. <tr>
  750. <td colspan="1" rowspan="1"
  751. valign="top" align="left">
  752. +E
  753. </td>
  754. <td colspan="1" rowspan="1"
  755. valign="top" align="left">
  756. build.compiler.emacs
  757. </td>
  758. <td colspan="1" rowspan="1"
  759. valign="top" align="left">
  760. false == not set
  761. </td>
  762. </tr>
  763. <tr>
  764. <td colspan="1" rowspan="1"
  765. valign="top" align="left">
  766. +P
  767. </td>
  768. <td colspan="1" rowspan="1"
  769. valign="top" align="left">
  770. build.compiler.pedantic
  771. </td>
  772. <td colspan="1" rowspan="1"
  773. valign="top" align="left">
  774. false == not set
  775. </td>
  776. </tr>
  777. <tr>
  778. <td colspan="1" rowspan="1"
  779. valign="top" align="left">
  780. +F
  781. </td>
  782. <td colspan="1" rowspan="1"
  783. valign="top" align="left">
  784. build.compiler.fulldepend
  785. </td>
  786. <td colspan="1" rowspan="1"
  787. valign="top" align="left">
  788. false == not set
  789. </td>
  790. </tr>
  791. <tr>
  792. <td colspan="1" rowspan="1"
  793. valign="top" align="left">
  794. <strong>(Only for Ant &lt; 1.4; replaced by the
  795. <code><strong>nowarn</strong></code>
  796. attribute of the <code><strong>&lt;javac&gt;</strong></code>
  797. task after that.)</strong><br />-nowarn
  798. </td>
  799. <td colspan="1" rowspan="1"
  800. valign="top" align="left">
  801. build.compiler.warnings
  802. </td>
  803. <td colspan="1" rowspan="1"
  804. valign="top" align="left">
  805. true == not set
  806. </td>
  807. </tr>
  808. </table>
  809. <p>With Ant &gt;= 1.5, you can also use nested
  810. <code>&lt;compilerarg&gt;</code> elements with the
  811. <code>&lt;javac&gt;</code> task.</p>
  812. <p class="faq">
  813. <a name="shell-redirect-1"></a>
  814. How do I include a &lt; character in my command-line arguments?
  815. </p>
  816. <p>The short answer is "Use: <code>&amp;lt;</code>".</p>
  817. <p>The long answer is that this probably won't do what you
  818. want anyway (see <a href="#shell-redirect-2">the next
  819. section</a>).</p>
  820. <p class="faq">
  821. <a name="shell-redirect-2"></a>
  822. How do I redirect standard input or standard output
  823. in the <code>&lt;exec&gt;</code> task?
  824. </p>
  825. <p>Say you want to redirect the standard output stream of the
  826. <code>m4</code> command to write to a file, something
  827. like:</p>
  828. <pre class="code">
  829. shell-prompt&gt; m4 foo.m4 &gt; foo
  830. </pre>
  831. <p>and try to translate it into</p>
  832. <pre class="code">
  833. &lt;exec executable=&quot;m4&quot;&gt;
  834. &lt;arg value=&quot;foo.m4&quot;/&gt;
  835. &lt;arg value=&quot;&amp;gt;&quot;/&gt;
  836. &lt;arg value=&quot;foo&quot;/&gt;
  837. &lt;/exec&gt;
  838. </pre>
  839. <p>This will not do what you expect. The output redirection is
  840. performed by your shell, not the command itself, so this
  841. should read:</p>
  842. <pre class="code">
  843. &lt;exec executable=&quot;/bin/sh&quot;&gt;
  844. &lt;arg value=&quot;-c&quot; /&gt;
  845. &lt;arg value=&quot;m4 foo.m4 &amp;gt; foo&quot; /&gt;
  846. &lt;/exec&gt;
  847. </pre>
  848. <p>Note that you must use the <code>value</code> attribute of
  849. <code>&lt;arg&gt;</code> in the last element, in order to have
  850. the command passed as a single, quoted argument. Alternatively,
  851. you can use:</p>
  852. <pre class="code">
  853. &lt;exec executable=&quot;/bin/sh&quot;&gt;
  854. &lt;arg line='-c &quot;m4 foo.m4 &amp;gt; foo&quot;'/&gt;
  855. &lt;/exec&gt;
  856. </pre>
  857. <p>Note the double-quotes nested inside the single-quotes.</p>
  858. <p class="faq">
  859. <a name="batch-shell-execute"></a>
  860. How do I execute a batch file or shell script from Ant?
  861. </p>
  862. <p>On native Unix systems, you should be able to run shell scripts
  863. directly. On systems running a Unix-type shell (for example, Cygwin
  864. on Windows) execute the (command) shell instead - <code>cmd</code>
  865. for batch files, <code>sh</code> for shell scripts - then pass the
  866. batch file or shell script (plus any arguments to the script)
  867. as a single command, using the <code>/c</code> or
  868. <code>-c</code> switch, respectively. See
  869. <a href="#shell-redirect-2">the above section</a>
  870. for example <code>&lt;exec&gt;</code> tasks
  871. executing <code>sh</code>. For batch files, use something like:</p>
  872. <pre class="code">
  873. &lt;exec dir=&quot;.&quot; executable=&quot;cmd&quot; os=&quot;Windows NT&quot;&gt;
  874. &lt;arg line=&quot;/c test.bat&quot;/&gt;
  875. &lt;/exec&gt;
  876. </pre>
  877. <p class="faq">
  878. <a name="multi-conditions"></a>
  879. I want to execute a particular target only if
  880. multiple conditions are true.
  881. </p>
  882. <p>There are actually several answers to this question.</p>
  883. <p>If you have only one set and one unset property to test,
  884. you can specify both an <code>if</code> and an <code>unless</code>
  885. attribute for the target, and they will act as if they
  886. are "anded" together.</p>
  887. <p>If you are using a version of Ant 1.3 or earlier, the
  888. way to work with all other cases is to chain targets together
  889. to determine the specific state you want to test for.</p>
  890. <p>To see how this works, assume you have three properties:
  891. <code>prop1</code>, <code>prop2</code>, and <code>prop3</code>.
  892. You want to test that <code>prop1</code> and <code>prop2</code>
  893. are set, and that <code>prop3</code> is not. If the condition
  894. holds true you want to echo "yes".</p>
  895. <p>Here is the implementation in Ant 1.3 and earlier:</p>
  896. <pre class="code">
  897. &lt;target name=&quot;cond&quot; depends=&quot;cond-if&quot;/&gt;
  898. &lt;target name=&quot;cond-if&quot; if=&quot;prop1&quot;&gt;
  899. &lt;antcall target=&quot;cond-if-2&quot;/&gt;
  900. &lt;/target&gt;
  901. &lt;target name=&quot;cond-if-2&quot; if=&quot;prop2&quot;&gt;
  902. &lt;antcall target=&quot;cond-if-3&quot;/&gt;
  903. &lt;/target&gt;
  904. &lt;target name=&quot;cond-if-3&quot; unless=&quot;prop3&quot;&gt;
  905. &lt;echo message=&quot;yes&quot;/&gt;
  906. &lt;/target&gt;
  907. </pre>
  908. <p>Note: <code>&lt;antcall&gt;</code> tasks do <em>not</em> pass
  909. property changes back up to the environment they were called
  910. from, so you wouldn't be able to, for example, set a
  911. <code>result</code> property in the <code>cond-if-3</code> target,
  912. then do
  913. <code>&lt;echo message="result is ${result}"/&gt;</code>
  914. in the <code>cond</code> target.</p>
  915. <p>Starting with Ant 1.4, you can use the
  916. <code>&lt;condition&gt;</code> task.</p>
  917. <pre class="code">
  918. &lt;target name=&quot;cond&quot; depends=&quot;cond-if,cond-else&quot;/&gt;
  919. &lt;target name=&quot;check-cond&quot;&gt;
  920. &lt;condition property=&quot;cond-is-true&quot;&gt;
  921. &lt;and&gt;
  922. &lt;not&gt;
  923. &lt;equals arg1=&quot;${prop1}&quot; arg2=&quot;$${prop1}&quot; /&gt;
  924. &lt;/not&gt;
  925. &lt;not&gt;
  926. &lt;equals arg1=&quot;${prop2}&quot; arg2=&quot;$${prop2}&quot; /&gt;
  927. &lt;/not&gt;
  928. &lt;equals arg1=&quot;${prop3}&quot; arg2=&quot;$${prop3}&quot; /&gt;
  929. &lt;/and&gt;
  930. &lt;/condition&gt;
  931. &lt;/target&gt;
  932. &lt;target name=&quot;cond-if&quot; depends=&quot;check-cond&quot; if=&quot;cond-is-true&quot;&gt;
  933. &lt;echo message=&quot;yes&quot;/&gt;
  934. &lt;/target&gt;
  935. &lt;target name=&quot;cond-else&quot; depends=&quot;check-cond&quot; unless=&quot;cond-is-true&quot;&gt;
  936. &lt;echo message=&quot;no&quot;/&gt;
  937. &lt;/target&gt;
  938. </pre>
  939. <p>This version takes advantage of two things:</p>
  940. <ul>
  941. <li>If a property <code>a</code> has not been set,
  942. <code>${a}</code> will evaluate to <code>${a}</code>.</li>
  943. <li>To get a literal <code>$</code> in Ant, you have to
  944. escape it with another <code>$</code> - this will also break
  945. the special treatment of the <code>${</code> sequence.</li>
  946. </ul>
  947. <p>Because testing for a literal <code>${property}</code> string
  948. isn't all that readable or easy to understand,
  949. post-1.4.1 Ant introduces the <code>&lt;isset&gt;</code> element
  950. to the <code>&lt;condition&gt;</code> task.</p>
  951. <p>Here is the previous example done using
  952. <code>&lt;isset&gt;</code>:</p>
  953. <pre class="code">
  954. &lt;target name=&quot;check-cond&quot;&gt;
  955. &lt;condition property=&quot;cond-is-true&quot;&gt;
  956. &lt;and&gt;
  957. &lt;isset property=&quot;prop1&quot;/&gt;
  958. &lt;isset property=&quot;prop2&quot;/&gt;
  959. &lt;not&gt;
  960. &lt;isset property=&quot;prop3&quot;/&gt;
  961. &lt;/not&gt;
  962. &lt;/and&gt;
  963. &lt;/condition&gt;
  964. &lt;/target&gt;
  965. </pre>
  966. <p>The last option is to use a scripting language to set the
  967. properties. This can be particularly handy when you need much
  968. finer control than the simple conditions shown here but, of
  969. course, comes with the overhead of adding JAR files to support
  970. the language, to say nothing of the added maintenance in requiring
  971. two languages to implement a single system. See the
  972. <a href="manual/OptionalTasks/script.html">
  973. <code>&lt;script&gt;</code> task documentation</a> for more
  974. details.</p>
  975. <p class="faq">
  976. <a name="encoding"></a>
  977. How can I include national characters like German
  978. umlauts in my build file?
  979. </p>
  980. <p>You need to tell the XML parser which character encoding
  981. your build file uses, this is done inside the <a href="http://www.w3.org/TR/2000/REC-xml-20001006#sec-prolog-dtd">XML
  982. declaration</a>.</p>
  983. <p>By default the parser assumes you are using the UTF-8
  984. encoding instead of your platform's default. For most Western
  985. European countries you should set the encoding to
  986. <code>ISO-8859-1</code>. To do so, make the very first line
  987. of you build file read like</p>
  988. <pre class="code">
  989. &lt;?xml version=&quot;1.0&quot; encoding=&quot;ISO-8859-1&quot; ?&gt;
  990. </pre>
  991. <p class="faq">
  992. <a name="use-zip-instead-of-jar"></a>
  993. How do I use <code>jar</code>'s <code>M</code> switch?
  994. I don't want a MANIFEST.
  995. </p>
  996. <p>A JAR archive is a ZIP file, so if you don't want a
  997. MANIFEST you can simply use <code>&lt;zip&gt;</code>.</p>
  998. <p>If your file names contain national characters you should
  999. know that Sun's <code>jar</code> utility like Ant's
  1000. <code>&lt;jar&gt;</code> uses UTF-8 to encode their names while
  1001. <code>&lt;zip&gt;</code> uses your platforms default encoding.
  1002. Use the encoding attribute of <code>&lt;zip&gt;</code> if
  1003. necessary.</p>
  1004. <p class="faq">
  1005. <a name="propertyvalue-as-name-for-property"></a>
  1006. How can I do something like <code>&lt;property name="prop"
  1007. value="${${anotherprop}}"/&gt;</code> (double expanding the property)?
  1008. </p>
  1009. <p>Without any external help you can not.</p>
  1010. <p>With &lt;script/&gt;, which needs external libraries, you can do</p>
  1011. <pre class="code">
  1012. &lt;script language=&quot;javascript&quot;&gt;
  1013. propname = project.getProperty(&quot;anotherprop&quot;);
  1014. project.setNewProperty(&quot;prop&quot;, propname);
  1015. &lt;/script&gt;
  1016. </pre>
  1017. <p>With AntContrib (external task library) you can do <code>
  1018. &lt;propertycopy name="prop" from="${anotherprop}"/&gt;</code>.</p>
  1019. <p>With Ant 1.6 you can simulate the AntContribs &lt;propertycopy&gt;
  1020. and avoid the need of an external library:</p>
  1021. <pre class="code">
  1022. &lt;macrodef name=&quot;propertycopy&quot;&gt;
  1023. &lt;attribute name=&quot;name&quot;/&gt;
  1024. &lt;attribute name=&quot;from&quot;/&gt;
  1025. &lt;sequential&gt;
  1026. &lt;property name=&quot;@{name}&quot; value=&quot;${@{from}}&quot;/&gt;
  1027. &lt;/sequential&gt;
  1028. &lt;/macrodef&gt;
  1029. </pre>
  1030. <p class="faq">
  1031. <a name="genral-advice"></a>
  1032. General Advice
  1033. </p>
  1034. <p>There are many reasons why Ant doesn't behave as
  1035. expected, not all of them are due to Ant bugs. See our <a href="problems.html">Having Problems?</a> page for hints that
  1036. may help pinning down the reasons for your problem.</p>
  1037. <p class="faq">
  1038. <a name="always-recompiles"></a>
  1039. Why does Ant always recompile all my Java files?
  1040. </p>
  1041. <p>In order to find out which files should be compiled, Ant
  1042. compares the timestamps of the source files to those of the
  1043. resulting <code>.class</code> files. Opening all source files
  1044. to find out which package they belong to would be very
  1045. inefficient. Instead, Ant expects you to place your
  1046. source files in a directory hierarchy that mirrors your
  1047. package hierarchy and to point Ant to the root of this
  1048. directory tree with the <code>srcdir</code> attribute.</p>
  1049. <p>Say you have <code>&lt;javac srcdir="src"
  1050. destdir="dest"/&gt;</code>. If Ant finds a file
  1051. <code>src/a/b/C.java</code>, it expects it to be in package
  1052. <code>a.b</code> so that the resulting <code>.class</code>
  1053. file is going to be <code>dest/a/b/C.class</code>.</p>
  1054. <p>If your source-tree directory structure does not match your
  1055. package structure, Ant's heuristic won't work, and
  1056. it will recompile classes that are up-to-date. Ant is not the
  1057. only tool that expects a source-tree layout like this.</p>
  1058. <p>If you have Java source files that aren't declared to
  1059. be part of any package, you can still use the <code>&lt;javac&gt;</code>
  1060. task to compile these files correctly - just set the
  1061. <code>srcdir</code> and <code>destdir</code> attributes to
  1062. the actual directory the source
  1063. files live in and the directory the class files should go into,
  1064. respectively.</p>
  1065. <p class="faq">
  1066. <a name="defaultexcludes"></a>
  1067. I've used a <code>&lt;delete&gt;</code> task to
  1068. delete unwanted SourceSafe control files (CVS files, editor
  1069. backup files, etc.), but it doesn't seem to work; the files
  1070. never get deleted. What's wrong?
  1071. </p>
  1072. <p>This is probably happening because, by default, Ant excludes
  1073. SourceSafe control files (<code>vssver.scc</code>) and certain other
  1074. files from FileSets.</p>
  1075. <p>Here's what you probably did:</p>
  1076. <pre class="code">
  1077. &lt;delete&gt;
  1078. &lt;fileset dir=&quot;${build.src}&quot; includes=&quot;**/vssver.scc&quot;/&gt;
  1079. &lt;/delete&gt;
  1080. </pre>
  1081. <p>You need to switch off the default exclusions,
  1082. and it will work:</p>
  1083. <pre class="code">
  1084. &lt;delete&gt;
  1085. &lt;fileset dir=&quot;${build.src}&quot; includes=&quot;**/vssver.scc&quot;
  1086. defaultexcludes=&quot;no&quot;/&gt;
  1087. &lt;/delete&gt;
  1088. </pre>
  1089. <p>For a complete listing of the patterns that are excluded
  1090. by default, see <a href="manual/dirtasks.html#defaultexcludes">the user
  1091. manual</a>.</p>
  1092. <p class="faq">
  1093. <a name="stop-dependency"></a>
  1094. I have a target I want to skip if a property is set,
  1095. so I have <code>unless="property"</code> as an attribute
  1096. of the target, but all the targets this target
  1097. depends on are still executed. Why?
  1098. </p>
  1099. <p>The list of dependencies is generated by Ant before any of the
  1100. targets are run. This allows dependent targets, such as an
  1101. <code>init</code> target, to set properties that can control the
  1102. execution of the targets higher in the dependency graph. This
  1103. is a good thing.</p>
  1104. <p>However, when your dependencies break down the
  1105. higher-level task
  1106. into several smaller steps, this behaviour becomes
  1107. counter-intuitive. There are a couple of solutions available:
  1108. </p>
  1109. <ol>
  1110. <li>Put the same condition on each of the dependent targets.</li>
  1111. <li>Execute the steps using <code>&lt;antcall&gt;</code>,
  1112. instead of specifying them inside the <code>depends</code>
  1113. attribute.</li>
  1114. </ol>
  1115. <p class="faq">
  1116. <a name="include-order"></a>
  1117. In my <code>&lt;fileset&gt;</code>, I've put in an
  1118. <code>&lt;exclude&gt;</code> of all files followed by an
  1119. <code>&lt;include&gt;</code> of just the files I want, but it
  1120. isn't giving me any files at all. What's wrong?
  1121. </p>
  1122. <p>The order of the <code>&lt;include&gt;</code> and
  1123. <code>&lt;exclude&gt;</code> tags within a <code>&lt;fileset&gt;</code>
  1124. is ignored when the FileSet is created. Instead, all of the
  1125. <code>&lt;include&gt;</code> elements are processed together,
  1126. followed by all of the <code>&lt;exclude&gt;</code>
  1127. elements. This means that the <code>&lt;exclude&gt;</code>
  1128. elements only apply to the file list produced by the
  1129. <code>&lt;include&gt;</code> elements.</p>
  1130. <p>To get the files you want, focus on just the
  1131. <code>&lt;include&gt;</code> patterns that would be necessary
  1132. to get them. If you find you need to trim the list that the
  1133. <code>&lt;include&gt;</code> elements produce, then use
  1134. <code>&lt;exclude&gt;</code> elements.</p>
  1135. <p class="faq">
  1136. <a name="properties-not-trimmed"></a>
  1137. <code>ant</code> failed to build my program via javac
  1138. even when I put the needed jars in an external
  1139. <code>build.properties</code> file and reference them by
  1140. <code>pathelement</code> or <code>classpath refid</code>.
  1141. </p>
  1142. <p>When <code>ant</code> loads properties from an external
  1143. file it doesn't touch the value of properties, trailing blanks
  1144. will not be trimmed for example.</p>
  1145. <p>If the value represents a file path, like a jar needed to
  1146. compile, the task which requires the value, javac for example
  1147. would fail to compile since it can't find the file due to
  1148. trailing spaces.</p>
  1149. <p class="faq">
  1150. <a name="winzip-lies"></a>
  1151. Ant creates WAR files with a lower-case
  1152. <code>web-inf</code> or JAR files with a lower-case
  1153. <code>meta-inf</code> directory.
  1154. </p>
  1155. <p>No it doesn't.</p>
  1156. <p>You may have seen these lower-case directory names in
  1157. WinZIP, but WinZIP is trying to be helpful (and fails). If
  1158. WinZIP encounters a filename that is all upper-case, it
  1159. assumes it has come from an old DOS box and changes the case to
  1160. all lower-case for you.</p>
  1161. <p>If you extract (or just check) the archive with jar, you
  1162. will see that the names have the correct case.</p>
  1163. <p>With WinZIP (version 8.1 at least), this can be corrected in the
  1164. configuration. In the Options/Configuration menu, in the View tab, General
  1165. section, check the "Allow all upper case files names" box. The META-INF and
  1166. WEB-INF will look correct.</p>
  1167. <p class="faq">
  1168. <a name="NoClassDefFoundError"></a>
  1169. I installed Ant 1.6.x and now get
  1170. <code>Exception in thread "main" java.lang.NoClassDefFoundError:
  1171. </code>
  1172. </p>
  1173. <p>
  1174. The cause of this is that there is an old version of ant somewhere in the
  1175. class path or configuration.
  1176. </p>
  1177. <p>
  1178. A version of this problem happens with jars that are in the classpath
  1179. that include an embedded copy of ant classes.
  1180. An example of this is some copies of weblogic.jar.
  1181. </p>
  1182. <p>
  1183. One can check if this is the case by doing (on unix/sh):
  1184. <code><pre>
  1185. unset CLASSPATH
  1186. ant -version
  1187. </pre>
  1188. </code>
  1189. </p>
  1190. <p class="faq">
  1191. <a name="InstantiationException"></a>
  1192. I installed Ant 1.6.x and now get
  1193. <code>java.lang.InstantiationException: org.apache.tools.ant.Main</code>
  1194. </p>
  1195. <p>
  1196. The cause of this is that there is an old version of ant somewhere in the
  1197. class path or configuration.
  1198. </p>
  1199. <p>
  1200. A version of this problem may be seen on some linux systems.
  1201. Some linux systems (Fedora Core 2 for example), comes with a version
  1202. of ant pre-installed. There is a configuration file called
  1203. <code>/etc/ant.conf</code> which if present, the ant shell
  1204. script will 'dot' include. On Fedora Core 2, the /etc/ant.conf
  1205. file resets the <code>ANT_HOME</code> environment variable to
  1206. <code>/usr/share/ant</code>. This causes the problem that
  1207. an old version of ant (1.5.x in this cause) will be used
  1208. with a new version of the ant script file.
  1209. </p>
  1210. <p>
  1211. One can check if this is the case by doing
  1212. <code>ant --noconfig -version</code>.
  1213. </p>
  1214. <p class="faq">
  1215. <a name="mangled-manifest"></a>
  1216. Whenever I use the Ant jar or manifest related tasks, long lines in
  1217. my manifest are wrapped at 70 characters and the resulting jar does
  1218. not work in my application server. Why does Ant do this?
  1219. </p>
  1220. <p>
  1221. Ant implements the Java
  1222. <a href="http://java.sun.com/j2se/1.4.2/docs/guide/jar/jar.html">Jar
  1223. file specification</a>. Please refer to the notes section where it
  1224. discusses the maximum allowable length of a line and the concept of
  1225. continuation characters.
  1226. </p>
  1227. <p>
  1228. If a jar file produced by Ant does not work in your appserver, and
  1229. that failure is due to the wrapped manifest, then you need
  1230. to consult your appserver provider, as it is a bug in their
  1231. appserver. Far more likely, however, is a problem in your
  1232. specification of your classpath. It is not Ant's wrapping of your
  1233. classpath that is the problem.
  1234. </p>
  1235. <p>
  1236. Do not raise a bug about this issue until you have checked to ensure
  1237. that the problem is not due to your classpath specification.
  1238. </p>
  1239. <p class="faq">
  1240. <a name="integration"></a>
  1241. Is Ant supported by my IDE/Editor?
  1242. </p>
  1243. <p>See the <a href="external.html#IDE and Editor Integration">section
  1244. on IDE integration</a> on our External Tools and Tasks page.</p>
  1245. <p class="faq">
  1246. <a name="emacs-mode"></a>
  1247. Why doesn't (X)Emacs/vi/MacOS X's project builder
  1248. correctly parse the error messages generated by Ant?
  1249. </p>
  1250. <p>Ant adds a "banner" with the name of the current
  1251. task in front of all logging messages - and there are no built-in
  1252. regular expressions in your editor that would account for
  1253. this.</p>
  1254. <p>You can disable this banner by invoking Ant with the
  1255. <code>-emacs</code> switch. To make Ant autodetect
  1256. Emacs' compile mode, put this into your
  1257. <code>.antrc</code> (contributed by Ville Skytt).</p>
  1258. <pre class="code">
  1259. # Detect (X)Emacs compile mode
  1260. if [ &quot;$EMACS&quot; = &quot;t&quot; ] ; then
  1261. ANT_ARGS=&quot;$ANT_ARGS -emacs&quot;
  1262. ANT_OPTS=&quot;$ANT_OPTS -Dbuild.compiler.emacs=true&quot;
  1263. fi
  1264. </pre>
  1265. <p>Alternatively, you can add the following snippet to your
  1266. <code>.emacs</code> to make Emacs understand Ant's
  1267. output.</p>
  1268. <pre class="code">
  1269. (require 'compile)
  1270. (setq compilation-error-regexp-alist
  1271. (append (list
  1272. ;; works for jikes
  1273. '(&quot;^\\s-*\\[[^]]*\\]\\s-*\\(.+\\):\\([0-9]+\\):\\([0-9]+\\):[0-9]+:[0-9]+:&quot; 1 2 3)
  1274. ;; works for javac
  1275. '(&quot;^\\s-*\\[[^]]*\\]\\s-*\\(.+\\):\\([0-9]+\\):&quot; 1 2))
  1276. compilation-error-regexp-alist))
  1277. </pre>
  1278. <p>Yet another alternative that preserves most of Ant's
  1279. formatting is to pipe Ant's output through the following Perl
  1280. script by Dirk-Willem van Gulik:</p>
  1281. <pre class="code">
  1282. #!/usr/bin/perl
  1283. #
  1284. # May 2001 dirkx@apache.org - remove any
  1285. # [foo] lines from the output; keeping
  1286. # spacing more or less there.
  1287. #
  1288. $|=1;
  1289. while(&lt;STDIN&gt;) {
  1290. if (s/^(\s+)\[(\w+)\]//) {
  1291. if ($2 ne $last) {
  1292. print &quot;$1\[$2\]&quot;;
  1293. $s = ' ' x length($2);
  1294. } else {
  1295. print &quot;$1 $s &quot;;
  1296. };
  1297. $last = $2;
  1298. };
  1299. print;
  1300. };
  1301. </pre>
  1302. <p class="faq">
  1303. <a name="dtd"></a>
  1304. Is there a DTD that I can use to validate my build
  1305. files?
  1306. </p>
  1307. <p>An incomplete DTD can be created by the
  1308. <code>&lt;antstructure&gt;</code> task - but this one
  1309. has a few problems:</p>
  1310. <ul>
  1311. <li>It doesn't know about required attributes. Only
  1312. manual tweaking of this file can help here.</li>
  1313. <li>It is not complete - if you add new tasks via
  1314. <code>&lt;taskdef&gt;</code> it won't know about it. See
  1315. <a href="http://www.sdv.fr/pages/casa/html/ant-dtd.en.html">this
  1316. page</a> by Michel Casabianca for a solution to this
  1317. problem. Note that the DTD you can download at this page
  1318. is based on Ant 0.3.1.</li>
  1319. <li>It may even be an invalid DTD. As Ant allows tasks
  1320. writers to define arbitrary elements, name collisions will
  1321. happen quite frequently - if your version of Ant contains
  1322. the optional <code>&lt;test&gt;</code> and
  1323. <code>&lt;junit&gt;</code> tasks, there are two XML
  1324. elements named <code>test</code> (the task and the nested child
  1325. element of <code>&lt;junit&gt;</code>) with different attribute
  1326. lists. This problem cannot be solved; DTDs don't give a
  1327. syntax rich enough to support this.</li>
  1328. </ul>
  1329. <p class="faq">
  1330. <a name="xml-entity-include"></a>
  1331. How do I include an XML snippet in my build file?
  1332. </p>
  1333. <p>You can use XML's way of including external files and let
  1334. the parser do the job for Ant:</p>
  1335. <pre class="code">
  1336. &lt;?xml version=&quot;1.0&quot;?&gt;
  1337. &lt;!DOCTYPE project [
  1338. &lt;!ENTITY common SYSTEM &quot;file:./common.xml&quot;&gt;
  1339. ]&gt;
  1340. &lt;project name=&quot;test&quot; default=&quot;test&quot; basedir=&quot;.&quot;&gt;
  1341. &lt;target name=&quot;setup&quot;&gt;
  1342. ...
  1343. &lt;/target&gt;
  1344. &amp;common;
  1345. ...
  1346. &lt;/project&gt;
  1347. </pre>
  1348. <p>will literally include the contents of <code>common.xml</code> where
  1349. you've placed the <code>&amp;common;</code> entity.</p>
  1350. <p>In combination with a DTD, this would look like this:</p>
  1351. <pre class="code">
  1352. &lt;!DOCTYPE project PUBLIC &quot;-//ANT//DTD project//EN&quot; &quot;file:./ant.dtd&quot; [
  1353. &lt;!ENTITY include SYSTEM &quot;file:./header.xml&quot;&gt;
  1354. ]&gt;
  1355. </pre>
  1356. <p>Starting with Ant 1.6, there is a new
  1357. <code>&lt;import&gt;</code> task that can (also) be used to
  1358. include build file fragments. Unlike the snippets used with
  1359. entity includes, the referenced files have to be complete Ant
  1360. build files, though.</p>
  1361. <p>The example above would become:</p>
  1362. <pre class="code">
  1363. &lt;?xml version=&quot;1.0&quot;?&gt;
  1364. &lt;project name=&quot;test&quot; default=&quot;test&quot; basedir=&quot;.&quot;&gt;
  1365. &lt;target name=&quot;setup&quot;&gt;
  1366. ...
  1367. &lt;/target&gt;
  1368. &lt;import file=&quot;./common.xml&quot;/&gt;
  1369. ...
  1370. &lt;/project&gt;
  1371. </pre>
  1372. <p>Unlike entity includes, <code>&lt;import&gt;</code> will
  1373. let you use Ant properties in the file name.</p>
  1374. <p class="faq">
  1375. <a name="mail-logger"></a>
  1376. How do I send an email with the result of my build
  1377. process?
  1378. </p>
  1379. <p>If you are using a nightly build of Ant 1.5 after
  1380. 2001-12-14, you can use the built-in MailLogger:</p>
  1381. <pre class="code">
  1382. ant -logger org.apache.tools.ant.listener.MailLogger
  1383. </pre>
  1384. <p>See the <a href="http://cvs.apache.org/viewcvs/~checkout~/ant/docs/manual/listeners.html?content-type=text/html">Listeners
  1385. &amp; Loggers</a> documentation for details on the properties
  1386. required.</p>
  1387. <p>For older versions of Ant, you can use a custom
  1388. BuildListener that sends out an email
  1389. in the buildFinished() method. Will Glozer
  1390. &lt;will.glozer@jda.com&gt; has written such a listener based
  1391. on <a href="http://java.sun.com/products/javamail/">JavaMail</a>.
  1392. The source is:</p>
  1393. <pre class="code">
  1394. import java.io.*;
  1395. import java.util.*;
  1396. import javax.mail.*;
  1397. import javax.mail.internet.*;
  1398. import org.apache.tools.ant.*;
  1399. /**
  1400. * A simple listener that waits for a build to finish and sends an email
  1401. * of the results. The settings are stored in &quot;monitor.properties&quot; and
  1402. * are fairly self explanatory.
  1403. *
  1404. * @author Will Glozer
  1405. * @version 1.05a 09/06/2000
  1406. */
  1407. public class BuildMonitor implements BuildListener {
  1408. protected Properties props;
  1409. /**
  1410. * Create a new BuildMonitor.
  1411. */
  1412. public BuildMonitor() throws Exception {
  1413. props = new Properties();
  1414. InputStream is = getClass().getResourceAsStream(&quot;monitor.properties&quot;);
  1415. props.load(is);
  1416. is.close();
  1417. }
  1418. public void buildStarted(BuildEvent e) {
  1419. }
  1420. /**
  1421. * Determine the status of the build and the actions to follow, now that
  1422. * the build has completed.
  1423. *
  1424. * @param e Event describing the build status.
  1425. */
  1426. public void buildFinished(BuildEvent e) {
  1427. Throwable th = e.getException();
  1428. String status = (th != null) ? &quot;failed&quot; : &quot;succeeded&quot;;
  1429. try {
  1430. String key = &quot;build.&quot; + status;
  1431. if (props.getProperty(key + &quot;.notify&quot;).equalsIgnoreCase(&quot;false&quot;)) {
  1432. return;
  1433. }
  1434. Session session = Session.getDefaultInstance(props, null);
  1435. MimeMessage message = new MimeMessage(session);
  1436. message.addRecipients(Message.RecipientType.TO, parseAddresses(
  1437. props.getProperty(key + &quot;.email.to&quot;)));
  1438. message.setSubject(props.getProperty(key + &quot;.email.subject&quot;));
  1439. BufferedReader br = new BufferedReader(new FileReader(
  1440. props.getProperty(&quot;build.log&quot;)));
  1441. StringWriter sw = new StringWriter();
  1442. String line = br.readLine();
  1443. while (line != null) {
  1444. sw.write(line);
  1445. sw.write(&quot;\n&quot;);
  1446. line = br.readLine();
  1447. }
  1448. br.close();
  1449. message.setText(sw.toString(), &quot;UTF-8&quot;);
  1450. sw.close();
  1451. Transport transport = session.getTransport();
  1452. transport.connect();
  1453. transport.send(message);
  1454. transport.close();
  1455. } catch (Exception ex) {
  1456. System.out.println(&quot;BuildMonitor failed to send email!&quot;);
  1457. ex.printStackTrace();
  1458. }
  1459. }
  1460. /**
  1461. * Parse a comma separated list of internet email addresses.
  1462. *
  1463. * @param s The list of addresses.
  1464. * @return Array of Addresses.
  1465. */
  1466. protected Address[] parseAddresses(String s) throws Exception {
  1467. StringTokenizer st = new StringTokenizer(s, &quot;,&quot;);
  1468. Address[] addrs = new Address[st.countTokens()];
  1469. for (int i = 0; i &lt; addrs.length; i++) {
  1470. addrs[i] = new InternetAddress(st.nextToken());
  1471. }
  1472. return addrs;
  1473. }
  1474. public void messageLogged(BuildEvent e) {
  1475. }
  1476. public void targetStarted(BuildEvent e) {
  1477. }
  1478. public void targetFinished(BuildEvent e) {
  1479. }
  1480. public void taskStarted(BuildEvent e) {
  1481. }
  1482. public void taskFinished(BuildEvent e) {
  1483. }
  1484. }
  1485. </pre>
  1486. <p>With a <code>monitor.properties</code> like this:</p>
  1487. <pre class="code">
  1488. # configuration for build monitor
  1489. mail.transport.protocol=smtp
  1490. mail.smtp.host=&lt;host&gt;
  1491. mail.from=Will Glozer &lt;will.glozer@jda.com&gt;
  1492. build.log=build.log
  1493. build.failed.notify=true
  1494. build.failed.email.to=will.glozer@jda.com
  1495. build.failed.email.subject=Nightly build failed!
  1496. build.succeeded.notify=true
  1497. build.succeeded.email.to=will.glozer@jda.com
  1498. build.succeeded.email.subject=Nightly build succeeded!
  1499. </pre>
  1500. <p><code>monitor.properties</code> should be placed right next
  1501. to your compiled <code>BuildMonitor.class</code>. To use it,
  1502. invoke Ant like:</p>
  1503. <pre class="code">
  1504. ant -listener BuildMonitor -logfile build.log
  1505. </pre>
  1506. <p>Make sure that <code>mail.jar</code> from JavaMail and
  1507. <code>activation.jar</code> from the
  1508. <a href="http://java.sun.com/products/javabeans/glasgow/jaf.html">Java
  1509. Beans Activation Framework</a> are in your <code>CLASSPATH</code>.</p>
  1510. <p class="faq">
  1511. <a name="listener-properties"></a>
  1512. How do I get at the properties that Ant was running
  1513. with from inside BuildListener?
  1514. </p>
  1515. <p>You can get at a hashtable with all the properties that Ant
  1516. has been using through the BuildEvent parameter. For
  1517. example:</p>
  1518. <pre class="code">
  1519. public void buildFinished(BuildEvent e) {
  1520. Hashtable table = e.getProject().getProperties();
  1521. String buildpath = (String)table.get(&quot;build.path&quot;);
  1522. ...
  1523. }
  1524. </pre>
  1525. <p>This is more accurate than just reading the same property
  1526. files that your project does, since it will give the correct
  1527. results for properties that were specified on the Ant command line.</p>
  1528. <p class="faq">
  1529. <a name="remove-cr"></a>
  1530. &lt;chmod&gt; or &lt;exec&gt; doesn't work in Ant
  1531. 1.3 on Unix
  1532. </p>
  1533. <p>The <code>antRun</code> script in <code>ANT_HOME/bin</code>
  1534. has DOS instead of Unix line endings; you must remove the
  1535. carriage-return characters from this file. This can be done by
  1536. using Ant's <code>&lt;fixcrlf&gt;</code> task
  1537. or something like:</p>
  1538. <pre class="code">
  1539. tr -d '\r' &lt; $ANT_HOME/bin/antRun &gt; /tmp/foo
  1540. mv /tmp/foo $ANT_HOME/bin/antRun
  1541. </pre>
  1542. <p class="faq">
  1543. <a name="javadoc-cannot-execute"></a>
  1544. JavaDoc failed: java.io.IOException: javadoc: cannot execute
  1545. </p>
  1546. <p>There is a bug in the Solaris reference implementation of
  1547. the JDK (see <a href="http://developer.java.sun.com/developer/bugParade/bugs/4230399.html">http://developer.java.sun.com/developer/bugParade/bugs/4230399.html</a>).
  1548. This also appears to be true under Linux. Moving the JDK to
  1549. the front of the PATH fixes the problem.</p>
  1550. <p class="faq">
  1551. <a name="delegating-classloader"></a>
  1552. &lt;style&gt; or &lt;junit&gt; ignores my
  1553. &lt;classpath&gt;
  1554. </p>
  1555. <p>These tasks don't ignore your classpath setting, you
  1556. are facing a common problem with delegating classloaders.</p>
  1557. <p>This question collects a common type of problem: A task
  1558. needs an external library and it has a nested classpath
  1559. element so that you can point it to this external library, but
  1560. that doesn't work unless you put the external library
  1561. into the <code>CLASSPATH</code> or place it in
  1562. <code>ANT_HOME/lib</code>.</p>
  1563. <p>Some background is necessary before we can discuss
  1564. solutions for <a href="#delegating-classloader-1.5">Ant
  1565. 1.5.x</a> and <a href="#delegating-classloader-1.6">Ant
  1566. 1.6.x</a>.</p>
  1567. <p>When you specify a nested <code>&lt;classpath&gt;</code> in
  1568. Ant, Ant creates a new class loader that uses the path you
  1569. have specified. It then tries to load additional classes from
  1570. this classloader.</p>
  1571. <p>In most cases - for example using &lt;style&gt; or
  1572. &lt;junit&gt; - Ant doesn't load the external library
  1573. directly, it is the loaded class that does so.</p>
  1574. <p>In the case of <code>&lt;junit&gt;</code> it is the task
  1575. implementation itself and in the case of
  1576. <code>&lt;style&gt;</code> it is the implementation of the
  1577. <code>org.apache.tools.ant.taskdefs.XSLTLiaison</code>
  1578. class.</p>
  1579. <p>Ant's class loader implementation uses Java's
  1580. delegation model, see <a href="http://java.sun.com/products/jdk/1.2/docs/api/java/lang/ClassLoader.html">http://java.sun.com/products/jdk/1.2/docs/api/java/lang/ClassLoader.html</a>
  1581. the paragraph</p>
  1582. <blockquote>The <code>ClassLoader</code> class uses a
  1583. delegation model to search for classes and resources. Each
  1584. instance of <code>ClassLoader</code> has an associated parent
  1585. class loader. When called upon to find a class or resource, a
  1586. <code>ClassLoader</code> instance will delegate the search for
  1587. the class or resource to its parent class loader before
  1588. attempting to find the class or resource itself. The virtual
  1589. machine's built-in class loader, called the bootstrap
  1590. class loader, does not itself have a parent but may serve as
  1591. the parent of a <code>ClassLoader</code>
  1592. instance.</blockquote>
  1593. <p>The possible solutions depend on the version of Ant you
  1594. use, see the next sections.</p>
  1595. <p class="faq">
  1596. <a name="delegating-classloader-1.5"></a>
  1597. &lt;style&gt; or &lt;junit&gt; ignores my
  1598. &lt;classpath&gt; - Ant 1.5.x version
  1599. </p>
  1600. <p>Please read <a href="#delegating-classloader">the previous
  1601. entry</a> before you go ahead.</p>
  1602. <p>First of all let's state that Ant's wrapper script
  1603. (<code>ant</code> or <code>ant.bat</code>) adds all
  1604. <code>.jar</code> files from <code>ANT_HOME/lib</code> to
  1605. <code>CLASSPATH</code>, therefore "in
  1606. <code>CLASSPATH</code>" shall mean "either in your
  1607. <code>CLASSPATH</code> environment variable or
  1608. <code>ANT_HOME/lib</code>" for the rest of this
  1609. answer.</p>
  1610. <p>The root of the problem is that the class that needs the
  1611. external library is on the <code>CLASSPATH</code>.</p>
  1612. <p>Let's see what happens when you load the &lt;junit&gt;
  1613. task. Ant's class loader will consult the
  1614. bootstrap class loader first, which tries to load classes from
  1615. <code>CLASSPATH</code>. The bootstrap class loader
  1616. doesn't know anything about Ant's class loader or
  1617. even the path you have specified.</p>
  1618. <p>If the bootstrap class loader can load the class Ant has
  1619. asked it to load (which it can if <code>optional.jar</code> is
  1620. part of <code>CLASSPATH</code>), this class will try to load
  1621. the external library from <code>CLASSPATH</code> as well - it
  1622. doesn't know anything else - and will not find it unless
  1623. the library is in <code>CLASSPATH</code> as well.</p>
  1624. <p>To solve this, you have two major options:</p>
  1625. <ol>
  1626. <li>put all external libraries you need in
  1627. <code>CLASSPATH</code> as well this is not what you want,
  1628. otherwise you wouldn't have found this FAQ entry.</li>
  1629. <li>remove the class that loads the external library from
  1630. the <code>CLASSPATH</code>.</li>
  1631. </ol>
  1632. <p>The easiest way to do this is to remove
  1633. <code>optional.jar</code> from <code>ANT_HOME/lib</code>. If
  1634. you do so, you will have to <code>&lt;taskdef&gt;</code> all
  1635. optional tasks and use nested <code>&lt;classpath&gt;</code>
  1636. elements in the <code>&lt;taskdef&gt;</code> tasks that point
  1637. to the new location of <code>optional.jar</code>. Also,
  1638. don't forget to add the new location of
  1639. <code>optional.jar</code> to the
  1640. <code>&lt;classpath&gt;</code> of your
  1641. <code>&lt;style&gt;</code> or <code>&lt;junit&gt;</code>
  1642. task.</p>
  1643. <p>If you want to avoid to <code>&lt;taskdef&gt;</code> all
  1644. optional tasks you need, the only other option is to remove
  1645. the classes that should not be loaded via the bootstrap class
  1646. loader from <code>optional.jar</code> and put them into a
  1647. separate archive. Add this separate archive to the
  1648. <code>&lt;classpath&gt;</code> of your
  1649. <code>&lt;style&gt;</code> or <code>&lt;junit&gt;</code> task
  1650. - and make sure the separate archive is not in
  1651. <code>CLASSPATH</code>.</p>
  1652. <p>In the case of <code>&lt;junit&gt;</code> you'd have
  1653. to remove all classes that are in the
  1654. <code>org/apache/tools/ant/taskdefs/optional/junit</code>
  1655. directory, in the <code>&lt;style&gt;</code> case it is one of
  1656. the <code>*Liaison</code> classes in
  1657. <code>org/apache/tools/ant/taskdefs/optional</code>.</p>
  1658. <p>If you use the option to break up <code>optional.jar</code>
  1659. for <code>&lt;junit&gt;</code> or remove
  1660. <code>ant-junit.jar</code>, you still have to use a
  1661. <code>&lt;taskdef&gt;</code> with a nested
  1662. <code>&lt;classpath&gt;</code> to define the junit task.</p>
  1663. <p class="faq">
  1664. <a name="delegating-classloader-1.6"></a>
  1665. &lt;style&gt; or &lt;junit&gt; ignores my
  1666. &lt;classpath&gt; - Ant 1.6.x version
  1667. </p>
  1668. <p>Please read <a href="#delegating-classloader">the general
  1669. entry</a> before you go ahead.</p>
  1670. <p>The wrapper script of Ant 1.6.x no longer adds the contents
  1671. of <code>ANT_HOME/lib</code> to <code>CLASSPATH</code>,
  1672. instead Ant will create a classloader on top of the bootstrap
  1673. classloader - let's call it the coreloader for the rest of
  1674. this answer - which holds the contents of
  1675. <code>ANT_HOME/lib</code>. Ant's core and its tasks will be
  1676. loaded through this classloader and not the bootstrap
  1677. classloader.</p>
  1678. <p>This causes some small but notable differences between Ant
  1679. 1.5.x and 1.6.x. Most importantly, a third-party task that is
  1680. part of <code>CLASSPATH</code> will no longer work in Ant
  1681. 1.6.x since the task now can't find Ant's classes. In a sense
  1682. this is the same problem this entry is about, only
  1683. <code>ant.jar</code> has become the external library in
  1684. question now.</p>
  1685. <p>This coreloader also holds the contents of
  1686. <code>~/.ant/lib</code> and any file or directory that has
  1687. been specified using Ant's <code>-lib</code> command line
  1688. argument.</p>
  1689. <p>Let's see what happens when you load the &lt;junit&gt;
  1690. task. Ant's class loader will consult the bootstrap
  1691. class loader first, which tries to load classes from
  1692. <code>CLASSPATH</code>. The bootstrap class loader
  1693. doesn't know anything about Ant's class loader or
  1694. even the path you have specified. If it fails to find the
  1695. class using the bootstrap classloader it will try the
  1696. coreloader next. Again, the coreloader doesn't know anything
  1697. about your path.</p>
  1698. <p>If the coreloader can load the class Ant has asked it to
  1699. load (which it can if <code>ant-junit.jar</code> is in
  1700. <code>ANT_HOME/lib</code>), this class will try to load the
  1701. external library from coreloader as well - it doesn't
  1702. know anything else - and will not find it unless the library
  1703. is in <code>CLASSPATH</code> or the coreloader as well.</p>
  1704. <p>To solve this, you have the following major options:</p>
  1705. <ol>
  1706. <li>put all external libraries you need in
  1707. <code>CLASSPATH</code> as well this is not what you want,
  1708. otherwise you wouldn't have found this FAQ entry.</li>
  1709. <li>put all external libraries you need in
  1710. <code>ANT_HOME/lib</code> or <code>.ant/lib</code>. This
  1711. probably still isn't what you want, but you might reconsider
  1712. the <code>.ant/lib</code> option.</li>
  1713. <li>Always start Ant with the <code>-lib</code> command line
  1714. switch and point to your external libraries (or the
  1715. directories holding them).</li>
  1716. <li>remove the class that loads the external library from
  1717. the coreloader.</li>
  1718. </ol>
  1719. <p>In Ant 1.6 <code>optional.jar</code> has been split into
  1720. multiple jars, each one containing classes with the same
  1721. dependencies on external libraries. You can move the
  1722. "offending" jar out of <code>ANT_HOME/lib</code>. For the
  1723. <code>&lt;junit&gt;</code> task it would be
  1724. <code>ant-junit.jar</code> and for <code>&lt;style&gt;</code>
  1725. it would be <code>ant-trax.jar</code>,
  1726. <code>ant-xalan1.jar</code> or <code>ant-xslp.jar</code> -
  1727. depending on the processor you use.</p>
  1728. <p>If you do so, you will have to <code>&lt;taskdef&gt;</code>
  1729. all optional tasks that need the external libary and use
  1730. nested <code>&lt;classpath&gt;</code> elements in the
  1731. <code>&lt;taskdef&gt;</code> tasks that point to the new
  1732. location of <code>ant-*.jar</code>. Also, don't forget
  1733. to add the new location of <code>ant-*.jar</code> to the
  1734. <code>&lt;classpath&gt;</code> of your
  1735. <code>&lt;style&gt;</code> or <code>&lt;junit&gt;</code>
  1736. task.</p>
  1737. <p>For example</p>
  1738. <pre class="code">
  1739. &lt;taskdef name=&quot;junit&quot;
  1740. class=&quot;org.apache.tools.ant.taskdefs.optional.junit.JUnitTask&quot;&gt;
  1741. &lt;classpath&gt;
  1742. &lt;pathelement location=&quot;HOME-OF/junit.jar&quot;/&gt;
  1743. &lt;pathelement location=&quot;NEW-HOME-OF/ant-junit.jar&quot;/&gt;
  1744. &lt;/classpath&gt;
  1745. &lt;/taskdef&gt;
  1746. </pre>
  1747. <p class="faq">
  1748. <a name="winxp-jdk14-ant14"></a>
  1749. When running Ant 1.4 on Windows XP and JDK 1.4, I get
  1750. various errors when trying to <code>&lt;exec&gt;</code>, fork
  1751. <code>&lt;java&gt;</code> or access environment
  1752. variables.
  1753. </p>
  1754. <p>Ant &lt; 1.5 doesn't recognize Windows XP as a flavor
  1755. of Windows that runs <code>CMD.EXE</code> instead of
  1756. <code>COMMAND.COM</code>. JDK 1.3 will tell Ant that Windows
  1757. XP is Windows 2000 so the problem doesn't show up
  1758. there.</p>
  1759. <p>Apart from upgrading to Ant 1.5 or better, setting the
  1760. environment variable <code>ANT_OPTS</code> to
  1761. <code>-Dos.name=Windows_NT</code> prior to invoking Ant has
  1762. been confirmed as a workaround.</p>
  1763. <p class="faq">
  1764. <a name="1.5-cygwin-sh"></a>
  1765. The <code>ant</code> wrapper script of Ant 1.5 fails
  1766. for Cygwin if <code>ANT_HOME</code> is set to a Windows style
  1767. path.
  1768. </p>
  1769. <p>This problem has been reported only hours after Ant 1.5 has
  1770. been released, see <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=10664">Bug
  1771. 10664</a> and all its duplicates.</p>
  1772. <p>A fixed version of the wrapper script can be found <a href="http://ant.apache.org/old-releases/v1.5/errata/">here</a>.
  1773. Simply replace your script with this version.</p>
  1774. <p class="faq">
  1775. <a name="1.5.2-zip-broken"></a>
  1776. <code>&lt;zip&gt;</code> is broken in Ant 1.5.2.
  1777. </p>
  1778. <p>Yes, it is.</p>
  1779. <p>The problem reported by most people - see <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=17648">Bug
  1780. 17648</a> and all its duplicates - is that Ant creates
  1781. archives that a partially unreadable by WinZIP. Luckily
  1782. <code>jar</code> deals with the archives and so the generated
  1783. jars/wars/ears will most likely work for you anyway.</p>
  1784. <p>There are additional problems, see bugs <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=17780">Bug
  1785. 17780</a>, <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=17871">Bug
  1786. 17871</a> and <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=18403">Bug
  1787. 18403</a>. All of them are supposed to be fixed with Ant
  1788. 1.5.3 (and only 18403 should exist in 1.5.3beta1).</p>
  1789. <p class="faq">
  1790. <a name="unknownelement.taskcontainer"></a>
  1791. Why do my custom task containers see Unknown Elements in Ant 1.6
  1792. - they worked in Ant 1.5?
  1793. </p>
  1794. <p>
  1795. The objects added in TaskContainer.addTask(Task task)
  1796. have changed from Tasks to UnknownElements.
  1797. </p>
  1798. <p>
  1799. There was a number of valid reasons for this change. But the backward
  1800. compatibility problems were not noticed until after Ant 1.6.0 was
  1801. released.
  1802. </p>
  1803. <p>
  1804. Your container class will need to be modified to check if the Task
  1805. is an UnknownElement and call perform on it to
  1806. convert it to a Task and to execute it.
  1807. (see apache.tools.ant.taskdefs.Sequential)
  1808. </p>
  1809. <p>
  1810. If you want to do more processing on the task,
  1811. you need to use the techniques in apache.tools.ant.taskdefs.Antlib#execute()
  1812. This does make use of one 1.6 method call (UE#getRealObject()),
  1813. you need to use UE#getTask() instead - this will
  1814. return null for non tasks (types like fileset id=x).
  1815. </p>
  1816. <p>
  1817. So.. iterate over the tasks, if they are UEs, convert them to
  1818. tasks, using UE#maybeConfigure and UE#getTask()
  1819. </p>
  1820. <pre class="code">
  1821. for (Iterator i = tasks.iterator(); i.hasNext();) {
  1822. Task t = (Task) i.next();
  1823. if (t instanceof UnknownElement) {
  1824. ((UnknownElement) t).maybeConfigure();
  1825. t = ((UnknownElement) t).getTask();
  1826. if (t == null) {
  1827. continue;
  1828. }
  1829. }
  1830. // .... original Custom code
  1831. }
  1832. </pre>
  1833. <p>
  1834. This approach should work for ant1.5 and ant1.6.
  1835. </p>
  1836. <p class="faq">
  1837. <a name="java.exception.stacktrace"></a>
  1838. The program I run via &lt;java&gt; throws an exception but I
  1839. can't seem to get the full stack trace.
  1840. </p>
  1841. <p>This is a know bug that has been fixed after the release of
  1842. Ant 1.6.1.</p>
  1843. <p>As a workaround, run your &lt;java&gt; task with
  1844. <code>fork="true"</code> and Ant will display the full
  1845. trace.</p>
  1846. <p class="faq">
  1847. <a name="junit-no-runtime-xml"></a>
  1848. Using format="xml", &lt;junit&gt; fails with a
  1849. <code>NoClassDefFoundError</code> if forked.
  1850. </p>
  1851. <p>The XML formatter needs the <a href="http://www.w3.org/DOM/">DOM classes</a> to work. If you
  1852. are using JDK 1.4 or later they are included with your Java
  1853. Runtime and this problem won't occur. If you are running JDK
  1854. 1.3 or earlier, the DOM classes have to be on your
  1855. &lt;junit&gt; task's &lt;classpath&gt;.</p>
  1856. <p>Prior to Ant 1.6.0 Ant would include the DOM classes from
  1857. the XML parser that is used by Ant itself if you set the
  1858. includeAntRuntime attribute to true (the default). With Ant
  1859. 1.6.0 this has been changed as this behavior made it
  1860. impossible to use a different XML parser in your tests.</p>
  1861. <p>This means that you have to take care of the DOM classes
  1862. explicitly starting with Ant 1.6.0. If you don't need to set
  1863. up a different XML parser for your tests, the easiest solution
  1864. is to add</p>
  1865. <pre class="code">
  1866. &lt;pathelement path=&quot;${ant.home}/lib/xml-apis.jar:${ant.home}/lib/xercesImpl.jar&quot;/&gt;
  1867. </pre>
  1868. <p>to your task's &lt;classpath&gt;.</p>
  1869. <p class="faq">
  1870. <a name="xalan-jdk1.5"></a>
  1871. <code>&lt;junitreport&gt;</code> doesn't work with JDK 1.5 but
  1872. worked fine with JDK 1.4.
  1873. </p>
  1874. <p>While JDK 1.4.x contains a version of Xalan-J 2, JDK 1.5
  1875. (and later?) have <a href="http://java.sun.com/j2se/1.5.0/compatibility.html#4959783">moved
  1876. to XSLTC</a>. Since this task uses Xalan's redirect
  1877. extensions for its internal stylesheet, Ant doesn't support
  1878. XSLTC yet. This means that you have to install <a href="http://xml.apache.org/xalan-j/">Xalan-J 2</a> in order
  1879. to use this task with JDK 1.5.</p>
  1880. <p>Starting with Ant 1.6.2 <code>&lt;junitreport&gt;</code>
  1881. supports JDK 1.5.</p>
  1882. </div>
  1883. </div>
  1884. <p class="copyright">
  1885. Copyright &copy; 2000-2005&nbsp;The Apache Software Foundation. All rights reserved.
  1886. <script type="text/javascript" language="JavaScript"><!--
  1887. document.write(" - "+"Last Published: " + document.lastModified);
  1888. // -->
  1889. </script>
  1890. </p>
  1891. </body>
  1892. </html>