From 5e41b698707d95b6e8e748d64dc6959a680663f8 Mon Sep 17 00:00:00 2001 From: Antoine Levy-Lambert Date: Mon, 21 Nov 2005 07:55:27 +0000 Subject: [PATCH] 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 --- docs/antnews.html | 5 +- docs/bindownload.html | 5 +- docs/bugs.html | 345 ++++++++++++++++++++++++++++++++++ docs/bylaws.html | 5 +- docs/contributors.html | 5 +- docs/external.html | 5 +- docs/faq.html | 7 +- docs/index.html | 5 +- docs/legal.html | 5 +- docs/license.html | 5 +- docs/mail.html | 5 +- docs/mission.html | 5 +- docs/problems.html | 160 ++-------------- docs/projects.html | 5 +- docs/resources.html | 5 +- docs/srcdownload.html | 5 +- docs/svn.html | 5 +- xdocs/bugs.xml | 168 +++++++++++++++++ xdocs/problems.xml | 154 ++------------- xdocs/stylesheets/project.xml | 3 +- 20 files changed, 570 insertions(+), 337 deletions(-) create mode 100644 docs/bugs.html create mode 100644 xdocs/bugs.xml diff --git a/docs/antnews.html b/docs/antnews.html index f145ba3f9..e814acc08 100644 --- a/docs/antnews.html +++ b/docs/antnews.html @@ -146,10 +146,7 @@ Subversion Repositories
  • - Bug Database -
    • -
  • - Enhancement Requests + Bug Database
  • Donations diff --git a/docs/bindownload.html b/docs/bindownload.html index ba8d7b0de..111afaaff 100644 --- a/docs/bindownload.html +++ b/docs/bindownload.html @@ -138,10 +138,7 @@ Subversion Repositories
  • - Bug Database -
    • -
  • - Enhancement Requests + Bug Database
  • Donations diff --git a/docs/bugs.html b/docs/bugs.html new file mode 100644 index 000000000..85568f33d --- /dev/null +++ b/docs/bugs.html @@ -0,0 +1,345 @@ + + + + + + + + Apache Ant - Bug database + + + + + + +

    + +

    + +
    + + + + + + +
    Apache Ant siteApache Ant logo +
    + + + + + + + + + + + + + + +
    + + + + +
    + the Apache Ant site +
    +
    +
    +
    + +
    + + + + + +
    + + + + +
    Home
    +     		+ + + + +
    Projects
    +
    +
    + +
    + +
    +
    + ApacheCon! +
    +
    + +
    + + +
    +
     
    +
    +
    +

    Bug database

    +

    + + Bug Database +

    +

    + This page gives you some bookmarks to use the Bugzilla + Apache Bug Database. +

    +

    + This link issues.apache.org connects you + to the complete list of Apache Bug Database systems. +

    +

    + + Has It Been Reported? +

    +

    + 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 + currently open 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 CC list to follow the progress + of this bug. +

    +

    Open Ant bugs by order of priority.

    +

    Open Ant bugs by number of votes.

    +

    + + Filing a Bug Report +

    +

    + Please read our document about problems + before deciding that there is an unreported + bug in Ant. +

    +

    + You have a few choices at this point. You can send + an email to the user 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. +

    +

    + 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. +

    +

    + To create the bug report hit this + + link. +

    +

    + + Asking for an Enhancement +

    +

    + 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 enhancement request. 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. +

    +

    + + Create an enhancement report + +

    +

    + + Fixing the Bug +

    +

    + 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 + + source distributions. If you + are going to tackle the problem at this level, you may want to + discuss some details first on the dev + mailing list. Once you have a fix for the problem, you may submit + the fix as a patch to either the + dev 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. +

    +

    + If you have a patch to submit and are sending it to the + dev mailing list, + prefix "[PATCH]" + to your message subject. Please include any relevant bug numbers. + Patch files should be created with the -u + option of the + diff or cvs diff command. For + example:

    + + diff -u Javac.java.orig Javac.java > javac.diffs

    +     + or, if you have source from CVS:

    + + cvs diff -u Javac.java > javac.diffs

    +     + + 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. +

    + +
    +
    + +

    + Copyright © 2000-2005 The Apache Software Foundation. All rights reserved. + +

    + + + + + + + + + + + + + diff --git a/docs/bylaws.html b/docs/bylaws.html index 9a38ff7f1..f769ac10b 100644 --- a/docs/bylaws.html +++ b/docs/bylaws.html @@ -140,10 +140,7 @@ Subversion Repositories
  • - Bug Database -
    • -
  • - Enhancement Requests + Bug Database
  • Donations diff --git a/docs/contributors.html b/docs/contributors.html index b5ded2d2b..aa297f395 100644 --- a/docs/contributors.html +++ b/docs/contributors.html @@ -140,10 +140,7 @@ Subversion Repositories
  • - Bug Database -
    • -
  • - Enhancement Requests + Bug Database
  • Donations diff --git a/docs/external.html b/docs/external.html index cac52a54a..3a8a4e265 100644 --- a/docs/external.html +++ b/docs/external.html @@ -140,10 +140,7 @@ Subversion Repositories
  • - Bug Database -
    • -
  • - Enhancement Requests + Bug Database
  • Donations diff --git a/docs/faq.html b/docs/faq.html index 857615bfb..2b3c0c883 100644 --- a/docs/faq.html +++ b/docs/faq.html @@ -140,10 +140,7 @@ Subversion Repositories
  • - Bug Database -
    • -
  • - Enhancement Requests + Bug Database
  • Donations @@ -1666,7 +1663,7 @@ mv /tmp/foo $ANT_HOME/bin/antRun org.apache.tools.ant.taskdefs.XSLTLiaison class.

    Ant's class loader implementation uses Java's - delegation model, see http://java.sun.com/j2se/1.5.0/docs/api/java/lang/ClassLoader.html + delegation model, see http://java.sun.com/products/jdk/1.2/docs/api/java/lang/ClassLoader.html the paragraph

    The ClassLoader class uses a delegation model to search for classes and resources. Each diff --git a/docs/index.html b/docs/index.html index d855bab68..60a4db32a 100644 --- a/docs/index.html +++ b/docs/index.html @@ -142,10 +142,7 @@ Subversion Repositories
  • - Bug Database -
    • -
  • - Enhancement Requests + Bug Database
  • Donations diff --git a/docs/legal.html b/docs/legal.html index 471bdeb9f..9346d0b12 100644 --- a/docs/legal.html +++ b/docs/legal.html @@ -140,10 +140,7 @@ Subversion Repositories
  • - Bug Database -
    • -
  • - Enhancement Requests + Bug Database
  • Donations diff --git a/docs/license.html b/docs/license.html index 8e7c62cad..90117a754 100644 --- a/docs/license.html +++ b/docs/license.html @@ -140,10 +140,7 @@ Subversion Repositories
  • - Bug Database -
    • -
  • - Enhancement Requests + Bug Database
  • Donations diff --git a/docs/mail.html b/docs/mail.html index 372ef0de3..b803a9f5e 100644 --- a/docs/mail.html +++ b/docs/mail.html @@ -140,10 +140,7 @@ Subversion Repositories
  • - Bug Database -
    • -
  • - Enhancement Requests + Bug Database
  • Donations diff --git a/docs/mission.html b/docs/mission.html index ab3de72fb..32cd8bde9 100644 --- a/docs/mission.html +++ b/docs/mission.html @@ -140,10 +140,7 @@ Subversion Repositories
  • - Bug Database -
    • -
  • - Enhancement Requests + Bug Database
  • Donations diff --git a/docs/problems.html b/docs/problems.html index 43a0f8d80..2c182ca85 100644 --- a/docs/problems.html +++ b/docs/problems.html @@ -140,10 +140,7 @@ Subversion Repositories
  • - Bug Database -
    • -
  • - Enhancement Requests + Bug Database
  • Donations @@ -240,7 +237,7 @@

    ant -v

    - + This will produce output that starts like the following:

    @@ -289,7 +286,7 @@ Complete build sequence is [debug, gensrc, compile, jar, test]
    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.

    @@ -330,143 +327,26 @@ D:\src\java\Unset.java
    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. While Ant nightly builds are typically quite - stable and are used by - Gump - 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 - - area. 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 svn.

    -

    - - Has It Been Reported? -

    -

    - 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 - Apache Bug Database. This system is easy to use, and it will - let you search the - currently open 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 CC list to follow the progress - of this bug. -

    -

    - - Filing a Bug Report -

    -

    - 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 user 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. -

    -

    - 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. -

    -

    - - Asking for an Enhancement -

    -

    - 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 enhancement request. 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. -

    -

    - - Fixing the Bug -

    -

    - 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 - - source distributions. If you - are going to tackle the problem at this level, you may want to - discuss some details first on the dev - mailing list. Once you have a fix for the problem, you may submit - the fix as a patch to either the - dev 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. -

    - If you have a patch to submit and are sending it to the - dev mailing list, - prefix "[PATCH]" - to your message subject. Please include any relevant bug numbers. - Patch files should be created with the -u - option of the - diff or cvs diff command. For - example:

    - - diff -u Javac.java.orig Javac.java > javac.diffs

    -     - or, if you have source from CVS:

    - - cvs diff -u Javac.java > javac.diffs

    -     - - 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. + Gump + 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.

    - +

    + We currently do not have nightly builds including the optional tasks. +

    +

    + + bugs +

    +

    If you ar convinced that you have identified an unfixed bug, please turn to + our document concerning the bug database.

    + diff --git a/docs/projects.html b/docs/projects.html index fdb525624..60a44dd62 100644 --- a/docs/projects.html +++ b/docs/projects.html @@ -140,10 +140,7 @@ Subversion Repositories
  • - Bug Database -
    • -
  • - Enhancement Requests + Bug Database
  • Donations diff --git a/docs/resources.html b/docs/resources.html index 70c714822..6cf1e6356 100644 --- a/docs/resources.html +++ b/docs/resources.html @@ -140,10 +140,7 @@ Subversion Repositories
  • - Bug Database -
    • -
  • - Enhancement Requests + Bug Database
  • Donations diff --git a/docs/srcdownload.html b/docs/srcdownload.html index 8e3af1695..2c83b6a42 100644 --- a/docs/srcdownload.html +++ b/docs/srcdownload.html @@ -138,10 +138,7 @@ Subversion Repositories
  • - Bug Database -
    • -
  • - Enhancement Requests + Bug Database
  • Donations diff --git a/docs/svn.html b/docs/svn.html index 4dad97ba0..dfbe332ea 100644 --- a/docs/svn.html +++ b/docs/svn.html @@ -140,10 +140,7 @@ Subversion Repositories
  • - Bug Database -
    • -
  • - Enhancement Requests + Bug Database
  • Donations diff --git a/xdocs/bugs.xml b/xdocs/bugs.xml new file mode 100644 index 000000000..6625af9f5 --- /dev/null +++ b/xdocs/bugs.xml @@ -0,0 +1,168 @@ + + + + + + Antoine Levy-Lambert + Bug database + + + +
    +

    + This page gives you some bookmarks to use the Bugzilla + Apache Bug Database. +

    +

    + This link issues.apache.org connects you + to the complete list of Apache Bug Database systems. +

    + +

    + 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 + currently open 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 CC list to follow the progress + of this bug. +

    +

    Open Ant bugs by order of priority.

    +

    Open Ant bugs by number of votes.

    +     + + +

    + Please read our document about problems + before deciding that there is an unreported + bug in Ant. +

    +

    + You have a few choices at this point. You can send + an email to the user 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. +

    +

    + 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. +

    +

    + To create the bug report hit this + + link. +

    +     + + +

    + 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 enhancement request. 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. +

    +

    + + Create an enhancement report + +

    +     + + +

    + 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 + + source distributions. If you + are going to tackle the problem at this level, you may want to + discuss some details first on the dev + mailing list. Once you have a fix for the problem, you may submit + the fix as a patch to either the + dev 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. +

    +

    + If you have a patch to submit and are sending it to the + dev mailing list, + prefix "[PATCH]" + to your message subject. Please include any relevant bug numbers. + Patch files should be created with the -u + option of the + diff or cvs diff command. For + example:



    + + diff -u Javac.java.orig Javac.java > javac.diffs



    +     + or, if you have source from CVS:



    + + cvs diff -u Javac.java > javac.diffs



    +     + + 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. +

    +     + + +
    + +     diff --git a/xdocs/problems.xml b/xdocs/problems.xml index 484acd59e..7f4eb73c6 100644 --- a/xdocs/problems.xml +++ b/xdocs/problems.xml @@ -33,7 +33,7 @@ you may encounter - these are just some suggestions to point you in the right direction.

    - +

    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, but many other problems are a result of an old version of Ant on your system as well.

    - +     @@ -84,7 +84,7 @@



    ant -v



    - + This will produce output that starts like the following:

    • @@ -130,7 +130,7 @@ Complete build sequence is [debug, gensrc, compile, jar, test]

    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.

    @@ -168,142 +168,28 @@ D:\src\java\Unset.java

    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. While Ant nightly builds are typically quite - stable and are used by - Gump - 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 - - area. 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 svn.

    - - - -

    - 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 - Apache Bug Database. This system is easy to use, and it will - let you search the - currently open 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 CC list to follow the progress - of this bug. -

    -     - - -

    - 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 user 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. -

    -

    - 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. -

    -     - - -

    - 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 enhancement request. 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. -

    -     - - -

    - 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 - - source distributions. If you - are going to tackle the problem at this level, you may want to - discuss some details first on the dev - mailing list. Once you have a fix for the problem, you may submit - the fix as a patch to either the - dev 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. -

    -

    - If you have a patch to submit and are sending it to the - dev mailing list, - prefix "[PATCH]" - to your message subject. Please include any relevant bug numbers. - Patch files should be created with the -u - option of the - diff or cvs diff command. For - example:



    - - diff -u Javac.java.orig Javac.java > javac.diffs



    -     - or, if you have source from CVS:



    - - cvs diff -u Javac.java > javac.diffs



    -     - - 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. +

    + Gump + 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. +

    +

    + We currently do not have nightly builds including the optional tasks.

    + +
    +

    If you ar convinced that you have identified an unfixed bug, please turn to + our document concerning the bug database.

    +
    diff --git a/xdocs/stylesheets/project.xml b/xdocs/stylesheets/project.xml index 6d4d023cd..b995303cf 100644 --- a/xdocs/stylesheets/project.xml +++ b/xdocs/stylesheets/project.xml @@ -52,8 +52,7 @@ - - +