youys
/
ant
Not watched
1
0
Fork 1
Code
Releases 0 Wiki Activity
Issues 0 Pull Requests 0 Datasets Model Cloudbrain
Browse Source

creation of a new document called bugs containing a part 

of what was in "problems".
updating some info.


git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@345865 13f79535-47bb-0310-9956-ffa450edef68
master
Antoine Levy-Lambert 19 years ago
parent
f6af37217e
commit
5e41b69870
20 changed files with 570 additions and 337 deletions
Split View
Diff Options
Show Stats Download Patch File Download Diff File
  1. +1
    -4
      docs/antnews.html
  2. +1
    -4
      docs/bindownload.html
  3. +345
    -0
      docs/bugs.html
  4. +1
    -4
      docs/bylaws.html
  5. +1
    -4
      docs/contributors.html
  6. +1
    -4
      docs/external.html
  7. +2
    -5
      docs/faq.html
  8. +1
    -4
      docs/index.html
  9. +1
    -4
      docs/legal.html
  10. +1
    -4
      docs/license.html
  11. +1
    -4
      docs/mail.html
  12. +1
    -4
      docs/mission.html
  13. +20
    -140
      docs/problems.html
  14. +1
    -4
      docs/projects.html
  15. +1
    -4
      docs/resources.html
  16. +1
    -4
      docs/srcdownload.html
  17. +1
    -4
      docs/svn.html
  18. +168
    -0
      xdocs/bugs.xml
  19. +20
    -134
      xdocs/problems.xml
  20. +1
    -2
      xdocs/stylesheets/project.xml

+ 1
- 4
docs/antnews.html View File

@@ -146,10 +146,7 @@
<a href="./svn.html">Subversion Repositories</a>
</li>
<li>
<a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant">Bug Database</a>
</li>
<li>
<a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant&amp;bug_severity=enhancement">Enhancement Requests</a>
<a href="./bugs.html">Bug Database</a>
</li>
<li>
<a href="http://www.apache.org/foundation/contributing.html">Donations</a>


+ 1
- 4
docs/bindownload.html View File

@@ -138,10 +138,7 @@
<a href="./svn.html">Subversion Repositories</a>
</li>
<li>
<a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant">Bug Database</a>
</li>
<li>
<a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant&amp;bug_severity=enhancement">Enhancement Requests</a>
<a href="./bugs.html">Bug Database</a>
</li>
<li>
<a href="http://www.apache.org/foundation/contributing.html">Donations</a>


+ 345
- 0
docs/bugs.html View File

@@ -0,0 +1,345 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html lang="en">
<!-- GENERATED FILE, DO NOT EDIT, EDIT THE XML FILE IN xdocs INSTEAD! -->
<head>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Apache Ant - Bug database</title>
<link type="text/css" href="./page.css" rel="stylesheet">
<meta name="author" content="Antoine Levy-Lambert">
<meta name="email" content="">
</head>
<body>
<p class="navpath">
<script src="./breadcrumbs.js" language="JavaScript" type="text/javascript"></script>
</p>
<div class="logobar">
<table width="100%" border="0" cellspacing="0" cellpadding="0">
<tr>
<td align="left"><img border="0" alt="Apache Ant site" src="./images/group-logo.gif"></td>
<td align="center" width="100%"><img alt="Apache Ant logo" border="0" src="./images/project-logo.gif"></td>
<td align="right">
<form target="_blank" onsubmit="q.value = query.value + ' site:ant.apache.org'" action="http://www.google.com/search" method="get">
<table summary="search" border="0" cellspacing="0" cellpadding="0" bgcolor="#4C6C8F">
<tr>
<td colspan="3"><img height="10" width="1" alt="" src="./images/spacer.gif"></td>
</tr>
<tr>
<td><img height="1" width="1" alt="" src="./images/spacer.gif"></td>
<td nowrap="nowrap" class="searchcaption">
<input name="q" type="hidden">
<input size="15" id="query" type="text">
<img height="1" width="5" alt="" src="./images/spacer.gif">
<input name="Search" value="Search" type="submit">
<br>
the Apache Ant site
</td>
<td><img height="1" width="1" alt="" src="./images/spacer.gif"></td>
</tr>
<tr>
<td><img alt="" border="0" height="10" width="9" src="./images/search-left.gif"></td>
<td><img height="1" width="1" alt="" src="./images/spacer.gif"></td>
<td><img alt="" border="0" height="10" width="9" src="./images/search-right.gif"></td>
</tr>
</table>
</form>
</td>
</tr>
</table>
</div>
<div class="tab">
<table summary="tab bar" border="0" cellpadding="0" cellspacing="0">
<tr>
<td width="8"><img alt="" height="5" width="8" src="./images/spacer.gif"></td><td valign="bottom">
<table summary="selected tab" style="height: 1.5em" border="0" cellpadding="0" cellspacing="0">
<tr>
<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>
</tr>
</table>
</td>
<td width="5"><img alt="" height="8" width="8" src="./images/spacer.gif"></td><td valign="bottom">
<table summary="non selected tab" style="height: 1.4em" border="0" cellpadding="0" cellspacing="0">
<tr>
<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>
</tr>
</table>
</td>
</tr>
</table>
</div>
<div class="bluebar"></div>
<div class="menucontainer">
<div align="center">
<a href="http://ApacheCon.Com/"><img width="125" height="125"
border="0" style="background-color: white"
src="http://www.apache.org/images/ac2005us_blue_125x125.jpg"
alt="ApacheCon!" title="Come to ApacheCon!"/></a>
</div>
<div class="menu">
<ul>
<li class="menuheader">Apache Ant
<ul>
<li>
<a href="./index.html">Welcome</a>
</li>
<li>
<a href="./license.html">License</a>
</li>
<li>
<a href="./antnews.html">News</a>
</li>
</ul>
</li>
<li class="menuheader">Documentation
<ul>
<li>
<a href="./manual/index.html">Manual</a>
</li>
<li>
<a href="./projects.html">Related Projects</a>
</li>
<li>
<a href="./external.html">External Tools and Tasks</a>
</li>
<li>
<a href="./resources.html">Resources</a>
</li>
<li>
<a href="./faq.html">Frequently Asked Questions</a>
</li>
<li>
<a href="http://wiki.apache.org/ant/FrontPage">Wiki</a>
</li>
<li>
<a href="./problems.html">Having Problems?</a>
</li>
</ul>
</li>
<li class="menuheader">Download
<ul>
<li>
<a href="http://ant.apache.org/bindownload.cgi">Binary Distributions</a>
</li>
<li>
<a href="http://ant.apache.org/srcdownload.cgi">Source Distributions</a>
</li>
</ul>
</li>
<li class="menuheader">Contributing
<ul>
<li>
<a href="./mail.html">Mailing Lists</a>
</li>
<li>
<a href="./svn.html">Subversion Repositories</a>
</li>
<li>
<a href="./bugs.html">Bug Database</a>
</li>
<li>
<a href="http://www.apache.org/foundation/contributing.html">Donations</a>
</li>
</ul>
</li>
<li class="menuheader">Project Management
<ul>
<li>
<a href="./contributors.html">Contributors</a>
</li>
<li>
<a href="./mission.html">Apache Ant Mission</a>
</li>
<li>
<a href="./bylaws.html">Project Bylaws</a>
</li>
<li>
<a href="./legal.html">Legal</a>
</li>
</ul>
</li>
</ul>
</div>
<img style="float: left" height="10" width="10" border="0" alt="" src="./images/menu-left.gif">
<img style="float: right" height="10" width="10" border="0" alt="" src="./images/menu-right.gif">
</div>
<div class="lightbluebar">&nbsp;</div>
<div class="main">
<div class="content">
<h1 class="title">Bug database</h1>
<h3 class="section">
<a name="Bug Database"></a>
Bug Database
</h3>
<p>
This page gives you some bookmarks to use the Bugzilla <a href="http://issues.apache.org/bugzilla/">
Apache Bug Database</a>.
</p>
<p>
This link <a href="http://issues.apache.org/">issues.apache.org</a> connects you
to the complete list of Apache Bug Database systems.
</p>
<h4 class="subsection">
<a name="Has It Been Reported?"></a>
Has It Been Reported?
</h4>
<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 . This system is easy to use, and it will
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">
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>
<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>
<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>
<h4 class="subsection">
<a name="Filing a Bug Report"></a>
Filing a Bug Report
</h4>
<p>
Please read our document about <a href="problems.html">problems</a>
before deciding that there is an unreported
bug in Ant.
</p>
<p>
You have a few choices at this point. You can send
an email to the <code>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>
<p>
To create the bug report hit this
<a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant">
link</a>.
</p>
<h4 class="subsection">
<a name="Asking for an Enhancement"></a>
Asking for an Enhancement
</h4>
<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>
<a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant&amp;bug_severity=enhancement">
Create an enhancement report</a>
</p>
<h4 class="subsection">
<a name="Fixing the Bug"></a>
Fixing the Bug
</h4>
<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
<a href="http://ant.apache.org/srcdownload.cgi">
source distributions</a>. If you
are going to tackle the problem at this level, you may want to
discuss some details first on the <code>dev</code>
mailing list. Once you have a fix for the problem, you may submit
the fix as a <i>patch</i> to either the
<code>dev</code> mailing
list, or enter the bug database as described above and attach the
patch to the bug report. Using the bug database has the advantage
of being able to track the progress of your patch.
</p>
<p>
If you have a patch to submit and are sending it to the
<code>dev</code> mailing list,
prefix "[PATCH]"
to your message subject. Please include any relevant bug numbers.
Patch files should be created with the <code>-u</code>
option of the
<code>diff</code> or <code>cvs diff</code> command. For
example:<br /><br />
<font face="verdana" size="-1">
diff -u Javac.java.orig Javac.java &gt; javac.diffs<br /><br />
</font>
or, if you have source from CVS:<br /><br />
<font face="verdana" size="-1">
cvs diff -u Javac.java &gt; javac.diffs<br /><br />
</font>
Note: You should give your patch files meaningful names.
This makes it easier for developers who need to apply a number
of different patch files.
</p>
</div>
</div>
<p class="copyright">
Copyright &copy; 2000-2005&nbsp;The Apache Software Foundation. All rights reserved.
<script type="text/javascript" language="JavaScript"><!--
document.write(" - "+"Last Published: " + document.lastModified);
// -->
</script>
</p>
</body>
</html>

+ 1
- 4
docs/bylaws.html View File

@@ -140,10 +140,7 @@
<a href="./svn.html">Subversion Repositories</a>
</li>
<li>
<a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant">Bug Database</a>
</li>
<li>
<a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant&amp;bug_severity=enhancement">Enhancement Requests</a>
<a href="./bugs.html">Bug Database</a>
</li>
<li>
<a href="http://www.apache.org/foundation/contributing.html">Donations</a>


+ 1
- 4
docs/contributors.html View File

@@ -140,10 +140,7 @@
<a href="./svn.html">Subversion Repositories</a>
</li>
<li>
<a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant">Bug Database</a>
</li>
<li>
<a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant&amp;bug_severity=enhancement">Enhancement Requests</a>
<a href="./bugs.html">Bug Database</a>
</li>
<li>
<a href="http://www.apache.org/foundation/contributing.html">Donations</a>


+ 1
- 4
docs/external.html View File

@@ -140,10 +140,7 @@
<a href="./svn.html">Subversion Repositories</a>
</li>
<li>
<a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant">Bug Database</a>
</li>
<li>
<a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant&amp;bug_severity=enhancement">Enhancement Requests</a>
<a href="./bugs.html">Bug Database</a>
</li>
<li>
<a href="http://www.apache.org/foundation/contributing.html">Donations</a>


+ 2
- 5
docs/faq.html View File

@@ -140,10 +140,7 @@
<a href="./svn.html">Subversion Repositories</a>
</li>
<li>
<a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant">Bug Database</a>
</li>
<li>
<a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant&amp;bug_severity=enhancement">Enhancement Requests</a>
<a href="./bugs.html">Bug Database</a>
</li>
<li>
<a href="http://www.apache.org/foundation/contributing.html">Donations</a>
@@ -1666,7 +1663,7 @@ mv /tmp/foo $ANT_HOME/bin/antRun
<code>org.apache.tools.ant.taskdefs.XSLTLiaison</code>
class.</p>
<p>Ant's class loader implementation uses Java's
delegation model, see <a href="http://java.sun.com/j2se/1.5.0/docs/api/java/lang/ClassLoader.html">http://java.sun.com/j2se/1.5.0/docs/api/java/lang/ClassLoader.html</a>
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>
the paragraph</p>
<blockquote>The <code>ClassLoader</code> class uses a
delegation model to search for classes and resources. Each


+ 1
- 4
docs/index.html View File

@@ -142,10 +142,7 @@
<a href="./svn.html">Subversion Repositories</a>
</li>
<li>
<a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant">Bug Database</a>
</li>
<li>
<a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant&amp;bug_severity=enhancement">Enhancement Requests</a>
<a href="./bugs.html">Bug Database</a>
</li>
<li>
<a href="http://www.apache.org/foundation/contributing.html">Donations</a>


+ 1
- 4
docs/legal.html View File

@@ -140,10 +140,7 @@
<a href="./svn.html">Subversion Repositories</a>
</li>
<li>
<a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant">Bug Database</a>
</li>
<li>
<a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant&amp;bug_severity=enhancement">Enhancement Requests</a>
<a href="./bugs.html">Bug Database</a>
</li>
<li>
<a href="http://www.apache.org/foundation/contributing.html">Donations</a>


+ 1
- 4
docs/license.html View File

@@ -140,10 +140,7 @@
<a href="./svn.html">Subversion Repositories</a>
</li>
<li>
<a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant">Bug Database</a>
</li>
<li>
<a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant&amp;bug_severity=enhancement">Enhancement Requests</a>
<a href="./bugs.html">Bug Database</a>
</li>
<li>
<a href="http://www.apache.org/foundation/contributing.html">Donations</a>


+ 1
- 4
docs/mail.html View File

@@ -140,10 +140,7 @@
<a href="./svn.html">Subversion Repositories</a>
</li>
<li>
<a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant">Bug Database</a>
</li>
<li>
<a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant&amp;bug_severity=enhancement">Enhancement Requests</a>
<a href="./bugs.html">Bug Database</a>
</li>
<li>
<a href="http://www.apache.org/foundation/contributing.html">Donations</a>


+ 1
- 4
docs/mission.html View File

@@ -140,10 +140,7 @@
<a href="./svn.html">Subversion Repositories</a>
</li>
<li>
<a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant">Bug Database</a>
</li>
<li>
<a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant&amp;bug_severity=enhancement">Enhancement Requests</a>
<a href="./bugs.html">Bug Database</a>
</li>
<li>
<a href="http://www.apache.org/foundation/contributing.html">Donations</a>


+ 20
- 140
docs/problems.html View File

@@ -140,10 +140,7 @@
<a href="./svn.html">Subversion Repositories</a>
</li>
<li>
<a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant">Bug Database</a>
</li>
<li>
<a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant&amp;bug_severity=enhancement">Enhancement Requests</a>
<a href="./bugs.html">Bug Database</a>
</li>
<li>
<a href="http://www.apache.org/foundation/contributing.html">Donations</a>
@@ -240,7 +237,7 @@
<br /><br />
<font face="verdana" size="-1">ant -v</font>
<br /><br />
This will produce output that starts like the following:</p>
<table class="ForrestTable" cellspacing="1" cellpadding="4">
<tr>
@@ -289,7 +286,7 @@ Complete build sequence is [debug, gensrc, compile, jar, test]<br />
skipping another.
This is followed by which compiler it will be using, the
arguments that will get passed to the compiler,
and a list of all the class files to be compiled.
and a list of all the class files to be compiled.
</p>
<table class="ForrestTable" cellspacing="1" cellpadding="4">
<tr>
@@ -330,143 +327,26 @@ D:\src\java\Unset.java<br />
After examining the debug output, if you still believe that the
problem you are having is caused by Ant, chances are that someone
else may have already encountered this problem, and perhaps it has
been fixed. The next step, therefore, may be to try a nightly build
of Ant to see if the problem has been fixed. <!--Nightly builds for Ant
are available from the
<a href="http://brutus.apache.org/~nightlybuild/builds/ant/">
Ant web site</a>.--> While Ant nightly builds are typically quite
stable and are used by
<a href="http://brutus.apache.org/gump/public/">Gump</a>
to build many other Jakarta projects, these builds should
nonetheless be treated as experimental. Note that nightly builds
do not build many of the optional tasks the come with Ant.
A snapshot of these optional tasks is occasionally uploaded to
the nightly download
<a href="http://cvs.apache.org/builds/ant/nightly/optional/">
area</a>. However, even this snapshot does not contain every
optional task.
been fixed. The next step, therefore, would be to download the
sources of ant, see <a href="svn.html">svn</a>.
</p>
<h4 class="subsection">
<a name="Has It Been Reported?"></a>
Has It Been Reported?
</h4>
<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://issues.apache.org/bugzilla/">
Apache Bug Database</a>. This system is easy to use, and it will
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">
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>
<h4 class="subsection">
<a name="Filing a Bug Report"></a>
Filing a Bug Report
</h4>
<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>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>
<h4 class="subsection">
<a name="Asking for an Enhancement"></a>
Asking for an Enhancement
</h4>
<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>
<h4 class="subsection">
<a name="Fixing the Bug"></a>
Fixing the Bug
</h4>
<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
<a href="http://ant.apache.org/srcdownload.cgi">
source distributions</a>. If you
are going to tackle the problem at this level, you may want to
discuss some details first on the <code>dev</code>
mailing list. Once you have a fix for the problem, you may submit
the fix as a <i>patch</i> to either the
<code>dev</code> mailing
list, or enter the bug database as described above and attach the
patch to the bug report. Using the bug database has the advantage
of being able to track the progress of your patch.
</p>
<p>
If you have a patch to submit and are sending it to the
<code>dev</code> mailing list,
prefix "[PATCH]"
to your message subject. Please include any relevant bug numbers.
Patch files should be created with the <code>-u</code>
option of the
<code>diff</code> or <code>cvs diff</code> command. For
example:<br /><br />
<font face="verdana" size="-1">
diff -u Javac.java.orig Javac.java &gt; javac.diffs<br /><br />
</font>
or, if you have source from CVS:<br /><br />
<font face="verdana" size="-1">
cvs diff -u Javac.java &gt; javac.diffs<br /><br />
</font>
Note: You should give your patch files meaningful names.
This makes it easier for developers who need to apply a number
of different patch files.
<a href="http://vmgump.apache.org/gump/public/index.html">Gump</a>
is building ant every night and using the ant built from the
latest source to build a long list of open source projects. However,
the version of ant built by gump is not available for download. Even
if it were, it would not include most of the optional tasks.
</p>
<p>
We currently do not have nightly builds including the optional tasks.
</p>
<h3 class="section">
<a name="bugs"></a>
bugs
</h3>
<p>If you ar convinced that you have identified an unfixed bug, please turn to
our document concerning the <a href="bugs.html">bug database</a>.</p>
</div>
</div>



+ 1
- 4
docs/projects.html View File

@@ -140,10 +140,7 @@
<a href="./svn.html">Subversion Repositories</a>
</li>
<li>
<a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant">Bug Database</a>
</li>
<li>
<a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant&amp;bug_severity=enhancement">Enhancement Requests</a>
<a href="./bugs.html">Bug Database</a>
</li>
<li>
<a href="http://www.apache.org/foundation/contributing.html">Donations</a>


+ 1
- 4
docs/resources.html View File

@@ -140,10 +140,7 @@
<a href="./svn.html">Subversion Repositories</a>
</li>
<li>
<a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant">Bug Database</a>
</li>
<li>
<a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant&amp;bug_severity=enhancement">Enhancement Requests</a>
<a href="./bugs.html">Bug Database</a>
</li>
<li>
<a href="http://www.apache.org/foundation/contributing.html">Donations</a>


+ 1
- 4
docs/srcdownload.html View File

@@ -138,10 +138,7 @@
<a href="./svn.html">Subversion Repositories</a>
</li>
<li>
<a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant">Bug Database</a>
</li>
<li>
<a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant&amp;bug_severity=enhancement">Enhancement Requests</a>
<a href="./bugs.html">Bug Database</a>
</li>
<li>
<a href="http://www.apache.org/foundation/contributing.html">Donations</a>


+ 1
- 4
docs/svn.html View File

@@ -140,10 +140,7 @@
<a href="./svn.html">Subversion Repositories</a>
</li>
<li>
<a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant">Bug Database</a>
</li>
<li>
<a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant&amp;bug_severity=enhancement">Enhancement Requests</a>
<a href="./bugs.html">Bug Database</a>
</li>
<li>
<a href="http://www.apache.org/foundation/contributing.html">Donations</a>


+ 168
- 0
xdocs/bugs.xml View File

@@ -0,0 +1,168 @@
<?xml version="1.0"?>
<!--
Copyright 2005 The Apache Software Foundation
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<document>
<properties>
<author email="">Antoine Levy-Lambert</author>
<title>Bug database</title>
</properties>
<body>
<section name="Bug Database">
<p>
This page gives you some bookmarks to use the Bugzilla <a href="http://issues.apache.org/bugzilla/">
Apache Bug Database</a>.
</p>
<p>
This link <a href="http://issues.apache.org/">issues.apache.org</a> connects you
to the complete list of Apache Bug Database systems.
</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 . This system is easy to use, and it will
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">
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>
<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>
<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>
</subsection>
<subsection name="Filing a Bug Report">
<p>
Please read our document about <a href="problems.html">problems</a>
before deciding that there is an unreported
bug in Ant.
</p>
<p>
You have a few choices at this point. You can send
an email to the <code>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>
<p>
To create the bug report hit this
<a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant">
link</a>.
</p>
</subsection>
<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 &quot;Enhancement&quot;. Just fill the bug report in,
set the severity of the bug to &quot;Enhancement&quot;, 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>
<a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant&amp;bug_severity=enhancement">
Create an enhancement report</a>
</p>
</subsection>
<subsection name="Fixing the 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
<a href="http://ant.apache.org/srcdownload.cgi">
source distributions</a>. If you
are going to tackle the problem at this level, you may want to
discuss some details first on the <code>dev</code>
mailing list. Once you have a fix for the problem, you may submit
the fix as a <i>patch</i> to either the
<code>dev</code> mailing
list, or enter the bug database as described above and attach the
patch to the bug report. Using the bug database has the advantage
of being able to track the progress of your patch.
</p>
<p>
If you have a patch to submit and are sending it to the
<code>dev</code> mailing list,
prefix &quot;[PATCH]&quot;
to your message subject. Please include any relevant bug numbers.
Patch files should be created with the <code>-u</code>
option of the
<code>diff</code> or <code>cvs diff</code> command. For
example:<br></br><br></br>
<font face="verdana" size="-1">
diff -u Javac.java.orig Javac.java &gt; javac.diffs<br></br><br></br>
</font>
or, if you have source from CVS:<br></br><br></br>
<font face="verdana" size="-1">
cvs diff -u Javac.java &gt; javac.diffs<br></br><br></br>
</font>
Note: You should give your patch files meaningful names.
This makes it easier for developers who need to apply a number
of different patch files.
</p>
</subsection>
</section>
</body>
</document>

+ 20
- 134
xdocs/problems.xml View File

@@ -33,7 +33,7 @@
you may encounter - these are just some suggestions to point
you in the right direction.
</p>
<subsection name="Ensure that you are actually running the version of Ant that you think you do">
<p>Many tools include a version of Ant and some Operating
Systems even install it by default now, so you may have a
@@ -57,7 +57,7 @@
href="faq.html#InstantiationException">examples</a>, but many
other problems are a result of an old version of Ant on your
system as well.</p>
</subsection>

<subsection name="Read the Manual">
@@ -84,7 +84,7 @@
<br></br><br></br>
<font face="verdana" size="-1">ant -v</font>
<br></br><br></br>
This will produce output that starts like the following:</p>
<table>
<tr>
@@ -130,7 +130,7 @@ Complete build sequence is [debug, gensrc, compile, jar, test]<br></br>
skipping another.
This is followed by which compiler it will be using, the
arguments that will get passed to the compiler,
and a list of all the class files to be compiled.
and a list of all the class files to be compiled.
</p>
<table>
<tr>
@@ -168,142 +168,28 @@ D:\src\java\Unset.java<br></br>
After examining the debug output, if you still believe that the
problem you are having is caused by Ant, chances are that someone
else may have already encountered this problem, and perhaps it has
been fixed. The next step, therefore, may be to try a nightly build
of Ant to see if the problem has been fixed. <!--Nightly builds for Ant
are available from the
<a href="http://brutus.apache.org/~nightlybuild/builds/ant/">
Ant web site</a>.--> While Ant nightly builds are typically quite
stable and are used by
<a href="http://brutus.apache.org/gump/public/">Gump</a>
to build many other Jakarta projects, these builds should
nonetheless be treated as experimental. Note that nightly builds
do not build many of the optional tasks the come with Ant.
A snapshot of these optional tasks is occasionally uploaded to
the nightly download
<a href="http://cvs.apache.org/builds/ant/nightly/optional/">
area</a>. However, even this snapshot does not contain every
optional task.
been fixed. The next step, therefore, would be to download the
sources of ant, see <a href="svn.html">svn</a>.
</p>
</subsection>
<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://issues.apache.org/bugzilla/">
Apache Bug Database</a>. This system is easy to use, and it will
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">
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 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>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 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 &quot;Enhancement&quot;. Just fill the bug report in,
set the severity of the bug to &quot;Enhancement&quot;, 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>
</subsection>
<subsection name="Fixing the 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
<a href="http://ant.apache.org/srcdownload.cgi">
source distributions</a>. If you
are going to tackle the problem at this level, you may want to
discuss some details first on the <code>dev</code>
mailing list. Once you have a fix for the problem, you may submit
the fix as a <i>patch</i> to either the
<code>dev</code> mailing
list, or enter the bug database as described above and attach the
patch to the bug report. Using the bug database has the advantage
of being able to track the progress of your patch.
</p>
<p>
If you have a patch to submit and are sending it to the
<code>dev</code> mailing list,
prefix &quot;[PATCH]&quot;
to your message subject. Please include any relevant bug numbers.
Patch files should be created with the <code>-u</code>
option of the
<code>diff</code> or <code>cvs diff</code> command. For
example:<br></br><br></br>
<font face="verdana" size="-1">
diff -u Javac.java.orig Javac.java &gt; javac.diffs<br></br><br></br>
</font>
or, if you have source from CVS:<br></br><br></br>
<font face="verdana" size="-1">
cvs diff -u Javac.java &gt; javac.diffs<br></br><br></br>
</font>
Note: You should give your patch files meaningful names.
This makes it easier for developers who need to apply a number
of different patch files.
<p>
<a href="http://vmgump.apache.org/gump/public/index.html">Gump</a>
is building ant every night and using the ant built from the
latest source to build a long list of open source projects. However,
the version of ant built by gump is not available for download. Even
if it were, it would not include most of the optional tasks.
</p>
<p>
We currently do not have nightly builds including the optional tasks.
</p>
</subsection>

</section>
<section name="bugs">
<p>If you ar convinced that you have identified an unfixed bug, please turn to
our document concerning the <a href="bugs.html">bug database</a>.</p>
</section>
</body>
</document>

+ 1
- 2
xdocs/stylesheets/project.xml View File

@@ -52,8 +52,7 @@
<menu name="Contributing">
<item name="Mailing Lists" href="/mail.html"/>
<item name="Subversion Repositories" href="/svn.html"/>
<item name="Bug Database" href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant"/>
<item name="Enhancement Requests" href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant&amp;amp;bug_severity=enhancement"/>
<item name="Bug Database" href="/bugs.html"/>
<item name="Donations" href="http://www.apache.org/foundation/contributing.html"/>
</menu>



Write Preview
Loading…
Cancel
Save