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.

bugs.html 20 KiB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376
  1. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
  2. <!--
  3. Licensed to the Apache Software Foundation (ASF) under one or more
  4. contributor license agreements. See the NOTICE file distributed with
  5. this work for additional information regarding copyright ownership.
  6. The ASF licenses this file to You under the Apache License, Version 2.0
  7. (the "License"); you may not use this file except in compliance with
  8. the License. You may obtain a copy of the License at
  9. http://www.apache.org/licenses/LICENSE-2.0
  10. Unless required by applicable law or agreed to in writing, software
  11. distributed under the License is distributed on an "AS IS" BASIS,
  12. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  13. See the License for the specific language governing permissions and
  14. limitations under the License.
  15. -->
  16. <html lang="en">
  17. <!-- GENERATED FILE, DO NOT EDIT, EDIT THE XML FILE IN xdocs INSTEAD! -->
  18. <head>
  19. <META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
  20. <title>Apache Ant - Bug database</title>
  21. <link type="text/css" href="./page.css" rel="stylesheet">
  22. <meta name="author" content="Antoine Levy-Lambert">
  23. <meta name="email" content="">
  24. </head>
  25. <body>
  26. <p class="navpath">
  27. <script src="./breadcrumbs.js" language="JavaScript" type="text/javascript"></script>
  28. </p>
  29. <div class="logobar">
  30. <table width="100%" border="0" cellspacing="0" cellpadding="0">
  31. <tr>
  32. <td align="left"><img border="0" alt="Apache Ant site" src="./images/group-logo.gif"></td>
  33. <td align="center" width="100%"><img alt="Apache Ant logo" border="0" src="./images/project-logo.gif"></td>
  34. <td align="right">
  35. <form target="_blank" onsubmit="q.value = query.value + ' site:ant.apache.org'" action="http://www.google.com/search" method="get">
  36. <table summary="search" border="0" cellspacing="0" cellpadding="0" bgcolor="#4C6C8F">
  37. <tr>
  38. <td colspan="3"><img height="10" width="1" alt="" src="./images/spacer.gif"></td>
  39. </tr>
  40. <tr>
  41. <td><img height="1" width="1" alt="" src="./images/spacer.gif"></td>
  42. <td nowrap="nowrap" class="searchcaption">
  43. <input name="q" type="hidden">
  44. <input size="15" id="query" type="text">
  45. <img height="1" width="5" alt="" src="./images/spacer.gif">
  46. <input name="Search" value="Search" type="submit">
  47. <br>
  48. the Apache Ant site
  49. </td>
  50. <td><img height="1" width="1" alt="" src="./images/spacer.gif"></td>
  51. </tr>
  52. <tr>
  53. <td><img alt="" border="0" height="10" width="9" src="./images/search-left.gif"></td>
  54. <td><img height="1" width="1" alt="" src="./images/spacer.gif"></td>
  55. <td><img alt="" border="0" height="10" width="9" src="./images/search-right.gif"></td>
  56. </tr>
  57. </table>
  58. </form>
  59. </td>
  60. </tr>
  61. </table>
  62. </div>
  63. <div class="tab">
  64. <table summary="tab bar" border="0" cellpadding="0" cellspacing="0">
  65. <tr>
  66. <td width="8"><img alt="" height="5" width="8" src="./images/spacer.gif"></td><td valign="bottom">
  67. <table summary="selected tab" style="height: 1.5em" border="0" cellpadding="0" cellspacing="0">
  68. <tr>
  69. <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>
  70. </tr>
  71. </table>
  72. </td>
  73. <td width="5"><img alt="" height="8" width="8" src="./images/spacer.gif"></td><td valign="bottom">
  74. <table summary="non selected tab" style="height: 1.4em" border="0" cellpadding="0" cellspacing="0">
  75. <tr>
  76. <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>
  77. </tr>
  78. </table>
  79. </td>
  80. </tr>
  81. </table>
  82. </div>
  83. <div class="bluebar"></div>
  84. <div class="menucontainer">
  85. <div class="menu">
  86. <ul>
  87. <li class="menuheader">Apache Ant
  88. <ul>
  89. <li>
  90. <a href="./index.html">Welcome</a>
  91. </li>
  92. <li>
  93. <a href="./license.html">License</a>
  94. </li>
  95. <li>
  96. <a href="./antnews.html">News</a>
  97. </li>
  98. </ul>
  99. </li>
  100. <li class="menuheader">Documentation
  101. <ul>
  102. <li>
  103. <a href="./manual/index.html">Manual</a>
  104. </li>
  105. <li>
  106. <a href="./projects.html">Related Projects</a>
  107. </li>
  108. <li>
  109. <a href="./external.html">External Tools and Tasks</a>
  110. </li>
  111. <li>
  112. <a href="./resources.html">Resources</a>
  113. </li>
  114. <li>
  115. <a href="./faq.html">Frequently Asked Questions</a>
  116. </li>
  117. <li>
  118. <a href="http://wiki.apache.org/ant/FrontPage">Wiki</a>
  119. </li>
  120. <li>
  121. <a href="./problems.html">Having Problems?</a>
  122. </li>
  123. </ul>
  124. </li>
  125. <li class="menuheader">Download
  126. <ul>
  127. <li>
  128. <a href="http://ant.apache.org/bindownload.cgi">Binary Distributions</a>
  129. </li>
  130. <li>
  131. <a href="http://ant.apache.org/srcdownload.cgi">Source Distributions</a>
  132. </li>
  133. </ul>
  134. </li>
  135. <li class="menuheader">Contributing
  136. <ul>
  137. <li>
  138. <a href="./mail.html">Mailing Lists</a>
  139. </li>
  140. <li>
  141. <a href="./svn.html">Subversion Repositories</a>
  142. </li>
  143. <li>
  144. <a href="./nightlies.html">Nightly+Continuous Builds</a>
  145. </li>
  146. <li>
  147. <a href="./bugs.html">Bug Database</a>
  148. </li>
  149. </ul>
  150. </li>
  151. <li class="menuheader">Sponsorship
  152. <ul>
  153. <li>
  154. <a href="http://www.apache.org/foundation/thanks.html">Thanks</a>
  155. </li>
  156. <li>
  157. <a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a>
  158. </li>
  159. <li>
  160. <a href="http://www.apache.org/foundation/contributing.html">Donations</a>
  161. </li>
  162. </ul>
  163. </li>
  164. <li class="menuheader">Project Management
  165. <ul>
  166. <li>
  167. <a href="./contributors.html">Contributors</a>
  168. </li>
  169. <li>
  170. <a href="./mission.html">Apache Ant Mission</a>
  171. </li>
  172. <li>
  173. <a href="./bylaws.html">Project Bylaws</a>
  174. </li>
  175. <li>
  176. <a href="./legal.html">Legal</a>
  177. </li>
  178. </ul>
  179. </li>
  180. </ul>
  181. </div>
  182. <center>
  183. <a href="http://www.apache.org/events/current-event.html"><img border="0" title="ApacheCon" alt="ApacheCon - logo" src="http://www.apache.org/events/current-event-125x125.png" style="width: 125px;height: 125px;"></a>
  184. </center>
  185. <img style="float: left" height="10" width="10" border="0" alt="" src="./images/menu-left.gif">
  186. <img style="float: right" height="10" width="10" border="0" alt="" src="./images/menu-right.gif">
  187. </div>
  188. <div class="lightbluebar">&nbsp;</div>
  189. <div class="main">
  190. <div class="content">
  191. <h1 class="title">Bug database</h1>
  192. <h3 class="section">
  193. <a name="Bug Database"></a>
  194. Bug Database
  195. </h3>
  196. <p>
  197. This page gives you some bookmarks to use the Bugzilla <a href="http://issues.apache.org/bugzilla/">
  198. Apache Bug Database</a>.
  199. </p>
  200. <p>
  201. This link <a href="http://issues.apache.org/">issues.apache.org</a> connects you
  202. to the complete list of Apache Bug Database systems.
  203. </p>
  204. <h4 class="subsection">
  205. <a name="Has It Been Reported?"></a>
  206. Has It Been Reported?
  207. </h4>
  208. <p>
  209. If the current nightly build doesn't resolve your problem, it is
  210. possible that someone else has reported the issue. It is time to
  211. look at the bug database. This system is easy to use, and it will
  212. 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">
  213. currently open</a> and resolved bugs to see if your problem has
  214. already been reported. If your problem has been reported, you can
  215. see whether any of the developers have commented, suggesting
  216. workarounds, or the reason for the bug, etc. Or you may have
  217. information to add (see about creating and modifying bug reports
  218. below), in which case, go right ahead and add the information.
  219. If you don't have any additional information, you may just want
  220. to vote for this bug, and perhaps
  221. add yourself to the <code>CC</code> list to follow the progress
  222. of this bug.
  223. </p>
  224. <p><a href="http://issues.apache.org/bugzilla/buglist.cgi?query_format=advanced&amp;short_desc_type=allwordssubstr&amp;short_desc=&amp;product=Ant&amp;long_desc_type=substring&amp;long_desc=&amp;bug_file_loc_type=allwordssubstr&amp;bug_file_loc=&amp;keywords_type=allwords&amp;keywords=&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;emailassigned_to1=1&amp;emailtype1=substring&amp;email1=&amp;emailassigned_to2=1&amp;emailreporter2=1&amp;emailcc2=1&amp;emailtype2=substring&amp;email2=&amp;bugidtype=include&amp;bug_id=&amp;votes=&amp;chfieldfrom=&amp;chfieldto=Now&amp;chfieldvalue=&amp;field0-0-0=noop&amp;type0-0-0=noop&amp;value0-0-0=">Open Ant bugs by order of priority</a>.</p>
  225. <p><a href="http://issues.apache.org/bugzilla/buglist.cgi?query_format=advanced&amp;short_desc_type=allwordssubstr&amp;short_desc=&amp;product=Ant&amp;long_desc_type=substring&amp;long_desc=&amp;bug_file_loc_type=allwordssubstr&amp;bug_file_loc=&amp;keywords_type=allwords&amp;keywords=&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;emailassigned_to1=1&amp;emailtype1=substring&amp;email1=&amp;emailassigned_to2=1&amp;emailreporter2=1&amp;emailcc2=1&amp;emailtype2=substring&amp;email2=&amp;bugidtype=include&amp;bug_id=&amp;votes=&amp;chfieldfrom=&amp;chfieldto=Now&amp;chfieldvalue=&amp;field0-0-0=noop&amp;type0-0-0=noop&amp;value0-0-0=&amp;order=bugs.votes,bugs.priority%2Cbugs.bug_severity&amp;query_based_on=">Open Ant bugs by number of votes</a>.</p>
  226. <h4 class="subsection">
  227. <a name="Filing a Bug Report"></a>
  228. Filing a Bug Report
  229. </h4>
  230. <p>
  231. Please read our document about <a href="problems.html">problems</a>
  232. before deciding that there is an unreported
  233. bug in Ant.
  234. </p>
  235. <p>
  236. You have a few choices at this point. You can send
  237. an email to the <code>user</code> mailing list
  238. to see if
  239. others have encountered your issue and find out how they may
  240. have worked around it. If after some discussion, you feel it
  241. is time to create
  242. a bug report, this is a simple operation in the bug database.
  243. Please try to provide as much information as possible in order
  244. to assist the developers in resolving the bug. Please try to enter
  245. correct values for the various inputs when creating the bug, such
  246. as which version of Ant you are running, and on which platform,
  247. etc. Once the bug is created, you can also add attachments to
  248. the bug report.
  249. </p>
  250. <p>
  251. What information should you include in your bug report? The
  252. easiest bugs to fix are those that are most easily reproducible,
  253. so it is really helpful if you can produce a small test case that
  254. exhibits the problem. In this case, you would attach the build file
  255. and any other files necessary to reproduce the problem, probably
  256. packed together in an archive. If you can't produce a test case,
  257. you should try to include a snippet from your build file and the
  258. relevant sections from the verbose or debug output from Ant. Try
  259. to include the header information where Ant states the version,
  260. the OS and VM information, etc. As debug output is likely to be
  261. very large, it's best to remove any output that is not
  262. relevant. Once the bug is entered into the bug database, you
  263. will be kept informed by email about progress on the bug. If
  264. you receive email asking for further information, please try to
  265. respond, as it will aid in the resolution of your bug.
  266. </p>
  267. <p>
  268. To create the bug report hit this
  269. <a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant">
  270. link</a>.
  271. </p>
  272. <h4 class="subsection">
  273. <a name="Asking for an Enhancement"></a>
  274. Asking for an Enhancement
  275. </h4>
  276. <p>
  277. Sometimes, you may find that Ant just doesn't do what you need it
  278. to. It isn't a bug, as such, since Ant is working the way it is
  279. supposed to work. Perhaps it is some additional functionality for
  280. a task that hasn't been thought of yet, or maybe a completely new
  281. task. For these situations, you will
  282. want to raise an <i>enhancement request</i>. Enhancement requests
  283. are managed using the same Apache Bug Database described above.
  284. These are just a different type of bug report. If you look in the
  285. bug database, you will see that one of the severity settings for
  286. a bug is "Enhancement". Just fill the bug report in,
  287. set the severity of the bug to "Enhancement", and
  288. state in the description how you would like to have Ant enhanced.
  289. Again, you should first check whether there are any existing
  290. enhancment requests that cover your needs. If so, just add your
  291. vote to these.
  292. </p>
  293. <p>
  294. <a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant&amp;bug_severity=enhancement">
  295. Create an enhancement report</a>
  296. </p>
  297. <h4 class="subsection">
  298. <a name="Fixing the Bug"></a>
  299. Fixing the Bug
  300. </h4>
  301. <p>
  302. If you aren't satisfied with just filing a bug report, you can
  303. try to find the cause of the problem and provide a fix yourself.
  304. The best way to do that is by working with the latest code from Subversion.
  305. Alternatively, you can work with the source code available from the
  306. <a href="http://ant.apache.org/srcdownload.cgi">
  307. source distributions</a>. If you
  308. are going to tackle the problem at this level, you may want to
  309. discuss some details first on the <code>dev</code>
  310. mailing list. Once you have a fix for the problem, you may submit
  311. the fix as a <i>patch</i> to either the
  312. <code>dev</code> mailing
  313. list, or enter the bug database as described above and attach the
  314. patch to the bug report. Using the bug database has the advantage
  315. of being able to track the progress of your patch.
  316. </p>
  317. <p>
  318. If you have a patch to submit and are sending it to the
  319. <code>dev</code> mailing list,
  320. prefix "[PATCH]"
  321. to your message subject (this is also a good idea for
  322. a subject line in the bug database).
  323. Please include any relevant bug numbers.
  324. Patch files should be created with the <code>-u</code>
  325. option of the
  326. <code>diff</code> or <code>svn diff</code> command. For
  327. example:<br /><br />
  328. <font face="verdana" size="-1">
  329. diff -u Javac.java.orig Javac.java &gt; javac.diffs<br /><br />
  330. </font>
  331. or, if you have source from Subversion:<br /><br />
  332. <font face="verdana" size="-1">
  333. svn diff Javac.java &gt; javac.diffs<br /><br />
  334. </font>
  335. Note: You should give your patch files meaningful names.
  336. This makes it easier for developers who need to apply a number
  337. of different patch files.
  338. </p>
  339. </div>
  340. </div>
  341. <p class="copyright">
  342. <script type="text/javascript" language="JavaScript"><!--
  343. document.write(" - "+"Last Published: " + document.lastModified);
  344. // -->
  345. </script>
  346. </p>
  347. </body>
  348. </html>