From b36f7bfbdf25bce97eacd1bdd1913172c5d11fbc Mon Sep 17 00:00:00 2001 From: Conor MacNeill Date: Mon, 6 Aug 2001 13:56:37 +0000 Subject: [PATCH] Forgot to regenerate after fixing typos git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@269477 13f79535-47bb-0310-9956-ffa450edef68 --- webpage/docs/problems.html | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/webpage/docs/problems.html b/webpage/docs/problems.html index 34f1aab23..e5f7c4265 100644 --- a/webpage/docs/problems.html +++ b/webpage/docs/problems.html @@ -94,7 +94,7 @@

If you are having problems with Ant, this page details some steps you can take to try and resolve the problem. If you can't resolve the problem then this page will help you collect some of the relevant information to provide a bug report. This information will help - the Ant developers understand and resolve the problem. Not all of the steps here will + the Ant developers understand and resolve the problem. Of course, not all of the steps here will make sense for every problem you encounter. These are just some suggestions to point you in the right direction.

@@ -108,7 +108,7 @@

The first step to take when you have a problem is to read the manual entry for the task or concept that is giving you trouble. Check particularly the meaning of - attributes and nested elements. Perhaps an attribute would proviude the behaviour you require. If you + attributes and nested elements. Perhaps an attribute would provide the behavior you require. If you have problems with the manual, then you can submit a documentation bug report (see below) to help us improve the Ant documentation.

@@ -175,7 +175,7 @@ check_for_optional_packages:

So, once you have all this debug information, how can you use it to solve your problem. That will depend on the task in question and the nature of your problem. Each task logs different aspects of its operation, but it will give you an idea of what is going on. For - example, the <javac> task logs the resons why it chooses to compile particular + example, the <javac> task logs the reasons why it chooses to compile particular classes and the equivalent command it is using. The following trace (which has been edited and reformatted for clarity) shows javac adding one class but skipping another. This is followed by the compiler arguments and a summary of all the classes to be compiled. @@ -285,7 +285,7 @@ check_for_optional_packages: 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 infromation as possible to assist the developers in resolving the bug. Please try to enter correct + 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.

@@ -314,7 +314,7 @@ check_for_optional_packages: 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 into the Bug + 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.