source: release-kits/lirk3/bin/ant-installer/web/manual/bugs.html@ 14982

Last change on this file since 14982 was 14982, checked in by oranfry, 16 years ago

initial import of LiRK3

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