Edit the right dang file this time! (Sure hope I'm doing this right
this time.)
Also add the JavaWorld finalist logo (unless for some reason people
don't want it up there).
PR:
Obtained from:
Submitted by:
Reviewed by:
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@271729 13f79535-47bb-0310-9956-ffa450edef68
<a name="Has it been reported?"><strong>Has it been reported?</strong></a>
<a name="Has It Been Reported?"><strong>Has It Been Reported?</strong></a>
</font>
</font>
</td></tr>
</td></tr>
<tr><td>
<tr><td>
<blockquote>
<blockquote>
<p>If the current nightly build doesn't resolve your problem, it is
<p>
If the current nightly build doesn't resolve your problem, it is
possible that someone else has reported the issue. It is time to
possible that someone else has reported the issue. It is time to
look at the <a href="http://nagoya.apache.org/bugzilla/">
look at the <a href="http://nagoya.apache.org/bugzilla/">
Apache Bug Database</a>. This system is easy to use, and it will
Apache Bug Database</a>. This system is easy to use, and it will
let you search the <a href="http://nagoya.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&product=Ant&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&order=bugs.bug_id">
let you search the <a href="http://nagoya.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&product=Ant&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&order=bugs.bug_id">
currently open</a> and resolved bugs to see if your problem has
already been reported. If your problem has been reported, you can
see whether any of the developers have commented, suggesting
workarounds, or the reason for the bug, etc. Or you may have
information to add (see about creating and modifying bug reports
below), in which case, go right ahead and add the information.
If you don't have any additional information, you may just want
to vote for this bug, and perhaps
add yourself to the <code>CC</code> list to follow the progress
of this bug.
currently open</a> and resolved bugs to see if your problem has
already been reported. If your problem has been reported, you can
see whether any of the developers have commented, suggesting
workarounds, or the reason for the bug, etc. Or you may have
information to add (see about creating and modifying bug reports
below), in which case, go right ahead and add the information.
If you don't have any additional information, you may just want
to vote for this bug, and perhaps
add yourself to the <code>CC</code> list to follow the progress
and resolved bugs to see if your problem has already been reported.
If your problem has been reported, you can see whether any of the developers have commented,
suggesting workarounds or the reason for the bug, etc. You may have more information to add (see about
creating bug reports below), in which case, go right ahead and add it. If you can't add more information
you may just want to vote for this bug, and perhaps add yourself to the CC list to follow the progress of
this bug.
</p>
<subsection name="Has It Been Reported?">
<p>
If the current nightly build doesn't resolve your problem, it is
possible that someone else has reported the issue. It is time to
look at the <a href="http://nagoya.apache.org/bugzilla/">
Apache Bug Database</a>. This system is easy to use, and it will
let you search the <a href="http://nagoya.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&product=Ant&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&order=bugs.bug_id">
currently open</a> and resolved bugs to see if your problem has
already been reported. If your problem has been reported, you can
see whether any of the developers have commented, suggesting
workarounds, or the reason for the bug, etc. Or you may have
information to add (see about creating and modifying bug reports
below), in which case, go right ahead and add the information.
If you don't have any additional information, you may just want
to vote for this bug, and perhaps
add yourself to the <code>CC</code> list to follow the progress
of this bug.
</p>
</subsection>
</subsection>
<subsection name="Filing a Bug report">
<p>By this time you may have decided that there is a bug in Ant. You have a few choices at this
point. You can send an email to the ant-user mailing list to see if others have encountered your issue
and how they may have worked around it. If after some discussion, you still feel you have a bug, it
is time to create a bug report. This is a simple operation in the Bug Database. Please try to provide
as much information as possible to assist the developers in resolving the bug. Please try to enter correct
values for the various inputs when creating the bug. Once the bug is created you can add attachments to
the bug report.
</p>
<p>What information should you include in your bug report? The easiest bugs to fix are those which are most
easily reproducible, so if you can, it is really helpful to produce a small test case that exhibits the
problem. In this case, you would attach the build file and other files necessary to reproduce the problem
probably packed together in an archive. If you can't produce a test case, you should try to include a
snippet from your build file and the relevant sections from the debug out from Ant. Try to include the
header information where Ant states the version, the OS and VM information etc. As the debug output is
likely to be very large, you should try to remove the output which is not relevant. Once the bug is
entered into the Bug Database, you will be kept informed about progress on the bug. If you receive email
asking for further information, please try to respond as it will aid in the resolution of your bug.
</p>
<subsection name="Filing a Bug Report">
<p>
By this time, you may have decided that there is an unreported
bug in Ant. You have a few choices at this point. You can send
an email to the <code>ant-user</code> mailing list to see if
others have encountered your issue and find out how they may
have worked around it. If after some discussion, you feel it
is time to create
a bug report, this is a simple operation in the bug database.
Please try to provide as much information as possible in order
to assist the developers in resolving the bug. Please try to enter
correct values for the various inputs when creating the bug, such
as which version of Ant you are running, and on which platform,
etc. Once the bug is created, you can also add attachments to
the bug report.
</p>
<p>
What information should you include in your bug report? The
easiest bugs to fix are those that are most easily reproducible,
so it is really helpful if you can produce a small test case that
exhibits the problem. In this case, you would attach the build file
and any other files necessary to reproduce the problem, probably
packed together in an archive. If you can't produce a test case,
you should try to include a snippet from your build file and the
relevant sections from the verbose or debug output from Ant. Try
to include the header information where Ant states the version,
the OS and VM information, etc. As debug output is likely to be
very large, it's best to remove any output that is not
relevant. Once the bug is entered into the bug database, you
will be kept informed by email about progress on the bug. If
you receive email asking for further information, please try to
respond, as it will aid in the resolution of your bug.
</p>
</subsection>
</subsection>
<subsection name="Asking for an enhancement">
<p>Sometimes, you may find that Ant just doesn't do what you want. It isn't a bug, as such, since Ant
is working the way it is supposed to. Perhaps it is something that hasn't been thought of yet, or
a completely new task. For these situations you will want to raise an enhancement request.
Enhancement requests are managed using the same Apache Bug Database described above.
These are just a different type of report. If you look in the database, you will see that one of
the severity settings for a bug is "Enhancement". So, just fill the bug report in, and
in the description, state how you would like to have Ant enhanced. Again you should check whether
there are any existing enhancment requests that cover your needs. If so, just add your vote to these.
<subsection name="Asking for an Enhancement">
<p>
Sometimes, you may find that Ant just doesn't do what you need it
to. It isn't a bug, as such, since Ant is working the way it is
supposed to work. Perhaps it is some additional functionality for
a task that hasn't been thought of yet, or maybe a completely new
task. For these situations, you will
want to raise an <i>enhancement request</i>. Enhancement requests
are managed using the same Apache Bug Database described above.
These are just a different type of bug report. If you look in the
bug database, you will see that one of the severity settings for
a bug is "Enhancement". Just fill the bug report in,
set the severity of the bug to "Enhancement", and
state in the description how you would like to have Ant enhanced.
Again, you should first check whether there are any existing
enhancment requests that cover your needs. If so, just add your
vote to these.
</p>
</p>
</subsection>
</subsection>
<subsection name="Fixing the Bug">
<subsection name="Fixing the Bug">
<p>If you aren't satisfied just filing a bug report, you can try to find and fix the problem yourself. The
best way to do that is by working against the latest code from CVS. Alternatively, you can work with the
source code from the source distributions available on the Jakarta website. If you are going to tackle the
issues at this level, you may want to discuss details on the ant-dev mailing list. Once you have a fix
for the problem, you may either submit the patch to the ant-dev mailing list or enter into the Bug
Database as described above, attaching the patch. Using the Bug database has the advantage of tracking
the progress of your bug.
<p>
If you aren't satisfied with just filing a bug report, you can
try to find the cause of the problem and provide a fix yourself.
The best way to do that is by working with the latest code from CVS.
Alternatively, you can work with the source code available from the
Thank you for your continuous support to the Openl Qizhi Community AI Collaboration Platform. In order to protect your usage rights and ensure network security, we updated the Openl Qizhi Community AI Collaboration Platform Usage Agreement in January 2024. The updated agreement specifies that users are prohibited from using intranet penetration tools. After you click "Agree and continue", you can continue to use our services. Thank you for your cooperation and understanding.
Diane Holt