ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From co...@apache.org
Subject cvs commit: jakarta-ant/webpage/xdocs/stylesheets project.xml
Date Mon, 06 Aug 2001 13:37:08 GMT
conor       01/08/06 06:37:08

  Modified:    webpage/docs antnews.html external.html faq.html index.html
                        logos.html resources.html
               webpage/xdocs/stylesheets project.xml
  Added:       webpage/docs problems.html
               webpage/xdocs problems.xml
  Log:
  Add a page to describe steps taken to resolve issues and how to submit
  useful bug reports.
  
  Revision  Changes    Path
  1.20      +2 -0      jakarta-ant/webpage/docs/antnews.html
  
  Index: antnews.html
  ===================================================================
  RCS file: /home/cvs/jakarta-ant/webpage/docs/antnews.html,v
  retrieving revision 1.19
  retrieving revision 1.20
  diff -u -r1.19 -r1.20
  --- antnews.html	2001/08/06 10:29:12	1.19
  +++ antnews.html	2001/08/06 13:37:08	1.20
  @@ -47,6 +47,8 @@
     </li>
             <li>      <a href="./faq.html">Ant FAQ</a>
     </li>
  +          <li>      <a href="./problems.html">Having Problems?</a>
  +  </li>
           </ul>
         <p><strong>Download</strong></p>
       <ul>
  
  
  
  1.25      +2 -0      jakarta-ant/webpage/docs/external.html
  
  Index: external.html
  ===================================================================
  RCS file: /home/cvs/jakarta-ant/webpage/docs/external.html,v
  retrieving revision 1.24
  retrieving revision 1.25
  diff -u -r1.24 -r1.25
  --- external.html	2001/07/23 14:50:26	1.24
  +++ external.html	2001/08/06 13:37:08	1.25
  @@ -45,6 +45,8 @@
     </li>
             <li>      <a href="./faq.html">Ant FAQ</a>
     </li>
  +          <li>      <a href="./problems.html">Having Problems?</a>
  +  </li>
           </ul>
         <p><strong>Download</strong></p>
       <ul>
  
  
  
  1.15      +2 -0      jakarta-ant/webpage/docs/faq.html
  
  Index: faq.html
  ===================================================================
  RCS file: /home/cvs/jakarta-ant/webpage/docs/faq.html,v
  retrieving revision 1.14
  retrieving revision 1.15
  diff -u -r1.14 -r1.15
  --- faq.html	2001/07/25 10:12:49	1.14
  +++ faq.html	2001/08/06 13:37:08	1.15
  @@ -45,6 +45,8 @@
     </li>
             <li>      <a href="./faq.html">Ant FAQ</a>
     </li>
  +          <li>      <a href="./problems.html">Having Problems?</a>
  +  </li>
           </ul>
         <p><strong>Download</strong></p>
       <ul>
  
  
  
  1.22      +2 -0      jakarta-ant/webpage/docs/index.html
  
  Index: index.html
  ===================================================================
  RCS file: /home/cvs/jakarta-ant/webpage/docs/index.html,v
  retrieving revision 1.21
  retrieving revision 1.22
  diff -u -r1.21 -r1.22
  --- index.html	2001/08/06 10:29:12	1.21
  +++ index.html	2001/08/06 13:37:08	1.22
  @@ -47,6 +47,8 @@
     </li>
             <li>      <a href="./faq.html">Ant FAQ</a>
     </li>
  +          <li>      <a href="./problems.html">Having Problems?</a>
  +  </li>
           </ul>
         <p><strong>Download</strong></p>
       <ul>
  
  
  
  1.13      +2 -0      jakarta-ant/webpage/docs/logos.html
  
  Index: logos.html
  ===================================================================
  RCS file: /home/cvs/jakarta-ant/webpage/docs/logos.html,v
  retrieving revision 1.12
  retrieving revision 1.13
  diff -u -r1.12 -r1.13
  --- logos.html	2001/07/18 06:13:52	1.12
  +++ logos.html	2001/08/06 13:37:08	1.13
  @@ -45,6 +45,8 @@
     </li>
             <li>      <a href="./faq.html">Ant FAQ</a>
     </li>
  +          <li>      <a href="./problems.html">Having Problems?</a>
  +  </li>
           </ul>
         <p><strong>Download</strong></p>
       <ul>
  
  
  
  1.13      +2 -0      jakarta-ant/webpage/docs/resources.html
  
  Index: resources.html
  ===================================================================
  RCS file: /home/cvs/jakarta-ant/webpage/docs/resources.html,v
  retrieving revision 1.12
  retrieving revision 1.13
  diff -u -r1.12 -r1.13
  --- resources.html	2001/07/16 06:54:42	1.12
  +++ resources.html	2001/08/06 13:37:08	1.13
  @@ -45,6 +45,8 @@
     </li>
             <li>      <a href="./faq.html">Ant FAQ</a>
     </li>
  +          <li>      <a href="./problems.html">Having Problems?</a>
  +  </li>
           </ul>
         <p><strong>Download</strong></p>
       <ul>
  
  
  
  1.1                  jakarta-ant/webpage/docs/problems.html
  
  Index: problems.html
  ===================================================================
  <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
  
  <!-- Content Stylesheet for Site -->
  
          
  <!-- start the processing -->
      <html>
      <head>
        <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
    
                        <meta name="author" value="Conor MacNeill">
    <meta name="email" value="conor@apache.org">
          
        <title>The Jakarta Site - Having Problems?</title>
      </head>
    
      <body bgcolor="#ffffff" text="#000000" link="#525D76">    
        <table border="0" width="100%" cellspacing="0">
          <!-- TOP IMAGE -->
          <tr>
                  <td colspan="2">
      <a href="http://jakarta.apache.org"><img src="http://jakarta.apache.org/images/jakarta-logo.gif"
align="left" border="0"/></a>
      </td>
            </tr>
        </table>
        <table border="0" width="100%" cellspacing="4">
          <tr><td colspan="2">
            <hr noshade="" size="1"/>
          </td></tr>
          
          <tr>
            <!-- LEFT SIDE NAVIGATION -->
            <td valign="top" nowrap="true">
                  <p><strong>Ant</strong></p>
      <ul>
            <li>      <a href="./index.html">Front Page</a>
    </li>
            <li>      <a href="./antnews.html">News</a>
    </li>
            <li>      <a href="./manual/">Documentation</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">Ant FAQ</a>
    </li>
            <li>      <a href="./problems.html">Having Problems?</a>
    </li>
          </ul>
        <p><strong>Download</strong></p>
      <ul>
            <li>      <a href="http://jakarta.apache.org/site/binindex.html">Binaries</a>
    </li>
            <li>      <a href="http://jakarta.apache.org/site/sourceindex.html">Source
Code</a>
    </li>
          </ul>
        <p><strong>Jakarta</strong></p>
      <ul>
            <li>      <a href="http://jakarta.apache.org/site/news.html">News
& Status</a>
    </li>
            <li>      <a href="http://jakarta.apache.org/site/mission.html">Mission</a>
    </li>
            <li>      <a href="http://jakarta.apache.org/site/guidelines.html">Guidelines
Notes</a>
    </li>
            <li>      <a href="http://jakarta.apache.org/site/faqs.html">FAQs</a>
    </li>
          </ul>
        <p><strong>Get Involved</strong></p>
      <ul>
            <li>      <a href="http://jakarta.apache.org/site/getinvolved.html">Overview</a>
    </li>
            <li>      <a href="http://jakarta.apache.org/site/cvsindex.html">CVS
Repositories</a>
    </li>
            <li>      <a href="http://jakarta.apache.org/site/mail.html">Mailing
Lists</a>
    </li>
            <li>      <a href="http://jakarta.apache.org/site/library.html">Reference
Library</a>
    </li>
            <li>      <a href="http://nagoya.apache.org/bugzilla/enter_bug.cgi?product=Ant">Bug
Database</a>
    </li>
            <li>      <a href="http://nagoya.apache.org/bugzilla/enter_bug.cgi?product=Ant&bug_severity=Enhancement">Enhancement
Requests</a>
    </li>
          </ul>
              </td>
            <td align="left" valign="top">
          <table border="0" cellspacing="0" cellpadding="2" width="100%">
      <tr><td bgcolor="#525D76">
        <font color="#ffffff" face="arial,helvetica,sanserif">
          <a name="Having Problems?"><strong>Having Problems?</strong></a>
        </font>
      </td></tr>
      <tr><td>
        <blockquote>
                          <p>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 
           make sense for every problem you encounter. These are just some suggestions to

           point you in the right direction.
        </p>
                                    <table border="0" cellspacing="0" cellpadding="2" width="100%">
      <tr><td bgcolor="#828DA6">
        <font color="#ffffff" face="arial,helvetica,sanserif">
          <a name="Read the Manual"><strong>Read the Manual</strong></a>
        </font>
      </td></tr>
      <tr><td>
        <blockquote>
                          <p>The first step to take when you have a problem is to read
the <a href="manual/">
             manual</a> 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
             have problems with the manual, then you can submit a documentation bug report
(see below) to help us
             improve the Ant documentation.
          </p>
                      </blockquote>
      </td></tr>
    </table>
                                    <table border="0" cellspacing="0" cellpadding="2" width="100%">
      <tr><td bgcolor="#828DA6">
        <font color="#ffffff" face="arial,helvetica,sanserif">
          <a name="Examine Debug Output"><strong>Examine Debug Output</strong></a>
        </font>
      </td></tr>
      <tr><td>
        <blockquote>
                          <p>The first step when you have a problem is to see what Ant
is doing. Try running Ant with
             The verbose flag<br /><br />
             <code>ant -verbose</code><br /><br />
             or<br /><br />
             <code>ant -v</code><br /><br />
             
             This will produce something which starts like the following:</p>
                                    <div align="left">
      <table cellspacing="4" cellpadding="0" border="0">
        <tr>
          <td bgcolor="#023264" width="1" height="1"><img src="/images/void.gif"
width="1" height="1" vspace="0" hspace="0" border="0"/></td>
          <td bgcolor="#023264" height="1"><img src="/images/void.gif" width="1"
height="1" vspace="0" hspace="0" border="0"/></td>
          <td bgcolor="#023264" width="1" height="1"><img src="/images/void.gif"
width="1" height="1" vspace="0" hspace="0" border="0"/></td>
        </tr>
        <tr>
          <td bgcolor="#023264" width="1"><img src="/images/void.gif" width="1" height="1"
vspace="0" hspace="0" border="0"/></td>
          <td bgcolor="#ffffff"><pre>
  Ant version 1.4alpha compiled on August 6 2001
  Buildfile: build.xml
  Detected Java version: 1.3 in: f:\jdk1.3\jre
  Detected OS: Windows NT
  parsing buildfile \jakarta-ant\build.xml with 
  URI = file:/jakarta-ant/build.xml
  Project base dir set to: \jakarta-ant
   [property] Loading \jakarta-ant\.ant.properties
   [property] Unable to find property file: \jakarta-ant\.ant.properties
   [property] Loading \conor\.ant.properties
   [property] Override ignored for debug
  
  prepare:
  
  check_for_optional_packages:
  ...
             </pre></td>
          <td bgcolor="#023264" width="1"><img src="/images/void.gif" width="1" height="1"
vspace="0" hspace="0" border="0"/></td>
        </tr>
        <tr>
          <td bgcolor="#023264" width="1" height="1"><img src="/images/void.gif"
width="1" height="1" vspace="0" hspace="0" border="0"/></td>
          <td bgcolor="#023264" height="1"><img src="/images/void.gif" width="1"
height="1" vspace="0" hspace="0" border="0"/></td>
          <td bgcolor="#023264" width="1" height="1"><img src="/images/void.gif"
width="1" height="1" vspace="0" hspace="0" border="0"/></td>
        </tr>
      </table>
    </div>
                                  <p>
               You may be able to see in this trace what ant is doing and why it takes a particular

               course of action. If you need even more information you can use the <code>-debug</code>

               flag rather than <code>-verbose</code>. This will generally produce
so much output that 
               you may want to save the output and analyze it in an editor.
             </p>
                                  <p>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 &lt;javac&gt; task logs the resons 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.

             </p>
                                    <div align="left">
      <table cellspacing="4" cellpadding="0" border="0">
        <tr>
          <td bgcolor="#023264" width="1" height="1"><img src="/images/void.gif"
width="1" height="1" vspace="0" hspace="0" border="0"/></td>
          <td bgcolor="#023264" height="1"><img src="/images/void.gif" width="1"
height="1" vspace="0" hspace="0" border="0"/></td>
          <td bgcolor="#023264" width="1" height="1"><img src="/images/void.gif"
width="1" height="1" vspace="0" hspace="0" border="0"/></td>
        </tr>
        <tr>
          <td bgcolor="#023264" width="1"><img src="/images/void.gif" width="1" height="1"
vspace="0" hspace="0" border="0"/></td>
          <td bgcolor="#ffffff"><pre>
   [javac] org\apache\tools\ant\listener\Log4jListener.java added as 
           \build\classes\org\apache\tools\ant\listener\Log4jListener.class 
               is outdated.
   [javac] org\apache\tools\ant\Location.java omitted as 
           \build\classes\org\apache\tools\ant\Location.class is up to date.
    ...
   [javac] Compiling 1 source file to \jakarta-ant\build\classes
   [javac] Using modern compiler
   [javac] Compilation args: -d \jakarta-ant\build\classes -classpath 
           \jakarta-ant\build\classes;F:\jdk1.3\lib\tools.jar;
           \Ant\lib\optional.jar;\Ant\lib\log4j.jar;
           \Ant\lib\junit.jar;\Ant\lib\jaxp.jar;
           \Ant\lib\crimson.jar;\Ant\lib\ant.jar 
           -sourcepath \jakarta-ant\src\main -g:none -O
      [javac] File to be compiled:
      \src\main\org\apache\tools\ant\listener\Log4jListener.java  
  </pre></td>
          <td bgcolor="#023264" width="1"><img src="/images/void.gif" width="1" height="1"
vspace="0" hspace="0" border="0"/></td>
        </tr>
        <tr>
          <td bgcolor="#023264" width="1" height="1"><img src="/images/void.gif"
width="1" height="1" vspace="0" hspace="0" border="0"/></td>
          <td bgcolor="#023264" height="1"><img src="/images/void.gif" width="1"
height="1" vspace="0" hspace="0" border="0"/></td>
          <td bgcolor="#023264" width="1" height="1"><img src="/images/void.gif"
width="1" height="1" vspace="0" hspace="0" border="0"/></td>
        </tr>
      </table>
    </div>
                                  <p>
                In many cases Ant tasks are wrappers around OS commands or other java classes.
In debug mode, many
                of these tasks will print out the equivalent command line, as the &lt;javac&gt;
task above does. If 
                you are having a problem, it is often useful to run the command directly in
the same way Ant is doing 
                and see if the problem persists. The problem may lie in the command being
run by Ant, or in the way 
                the Ant task is running the command. You can also see the effect of changing
attribute values on the
                generated command line. This can help you to understand whether you are using
the correct attributes
                and values.
              </p>
                      </blockquote>
      </td></tr>
    </table>
                                    <table border="0" cellspacing="0" cellpadding="2" width="100%">
      <tr><td bgcolor="#828DA6">
        <font color="#ffffff" face="arial,helvetica,sanserif">
          <a name="Has it been fixed?"><strong>Has it been fixed?</strong></a>
        </font>
      </td></tr>
      <tr><td>
        <blockquote>
                          <p>
            After examining the debug output, you still believe that the problem you are having
may be 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="/builds/jakarta-ant/nightly/">Jakarta web site</a>. While
Ant nightly
            builds are typically quite stable and are used by <a href="/builds/gump/latest/">
            Gump</a> to build many other Jakarta projects, these builds should be treated
as experimental. You can 
            install and verify whether your problem has been fixed. 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="/builds/jakarta-ant/nightly/optional/">area</a>.
Note that even 
            this snapshot does not contain every optional task.
          </p>
                      </blockquote>
      </td></tr>
    </table>
                                    <table border="0" cellspacing="0" cellpadding="2" width="100%">
      <tr><td bgcolor="#828DA6">
        <font color="#ffffff" face="arial,helvetica,sanserif">
          <a name="Has it been reported?"><strong>Has it been reported?</strong></a>
        </font>
      </td></tr>
      <tr><td>
        <blockquote>
                          <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 currently open and resolved
bugs to see if your
            problem has already been reported. If it has, 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>
                      </blockquote>
      </td></tr>
    </table>
                                    <table border="0" cellspacing="0" cellpadding="2" width="100%">
      <tr><td bgcolor="#828DA6">
        <font color="#ffffff" face="arial,helvetica,sanserif">
          <a name="Filing a Bug report"><strong>Filing a Bug report</strong></a>
        </font>
      </td></tr>
      <tr><td>
        <blockquote>
                          <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 infromation 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>
                      </blockquote>
      </td></tr>
    </table>
                                    <table border="0" cellspacing="0" cellpadding="2" width="100%">
      <tr><td bgcolor="#828DA6">
        <font color="#ffffff" face="arial,helvetica,sanserif">
          <a name="Fixing the Bug"><strong>Fixing the Bug</strong></a>
        </font>
      </td></tr>
      <tr><td>
        <blockquote>
                          <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 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>
                      </blockquote>
      </td></tr>
    </table>
                      </blockquote>
      </td></tr>
    </table>
                </td>
          </tr>
  
          <!-- FOOTER -->
          <tr><td colspan="2">
            <hr noshade="" size="1"/>
          </td></tr>
          <tr><td colspan="2">
            <div align="center"><font color="#525D76" size="-1"><em>
            Copyright &#169; 1999-2001, Apache Software Foundation
            </em></font></div>
          </td></tr>
        </table>
      </body>
    </html>
  <!-- end the processing -->
  
  
  
  
  
  
  
  1.1                  jakarta-ant/webpage/xdocs/problems.xml
  
  Index: problems.xml
  ===================================================================
  <?xml version="1.0"?>
  <document>
  
    <properties>
      <author email="conor@apache.org">Conor MacNeill</author>
      <title>Having Problems?</title>
    </properties>
  
    <body>
      <section name="Having Problems?">
        <p>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. 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.
        </p>
           
        <subsection name="Read the Manual">
          <p>The first step to take when you have a problem is to read the <a href="manual/">
             manual</a> entry for the task or concept that is giving you trouble. Check
particularly the meaning of
             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.
          </p>        
        </subsection>
        <subsection name="Examine Debug Output">
          <p>The first step when you have a problem is to see what Ant is doing. Try
running Ant with
             The verbose flag<br/><br/>
             <code>ant -verbose</code><br/><br/>
             or<br/><br/>
             <code>ant -v</code><br/><br/>
             
             This will produce something which starts like the following:</p>
             <source>
  Ant version 1.4alpha compiled on August 6 2001
  Buildfile: build.xml
  Detected Java version: 1.3 in: f:\jdk1.3\jre
  Detected OS: Windows NT
  parsing buildfile \jakarta-ant\build.xml with 
  URI = file:/jakarta-ant/build.xml
  Project base dir set to: \jakarta-ant
   [property] Loading \jakarta-ant\.ant.properties
   [property] Unable to find property file: \jakarta-ant\.ant.properties
   [property] Loading \conor\.ant.properties
   [property] Override ignored for debug
  
  prepare:
  
  check_for_optional_packages:
  ...
             </source>
             <p>
               You may be able to see in this trace what ant is doing and why it takes a particular

               course of action. If you need even more information you can use the <code>-debug</code>

               flag rather than <code>-verbose</code>. This will generally produce
so much output that 
               you may want to save the output and analyze it in an editor.
             </p>
             
             <p>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 &lt;javac&gt; 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.

             </p>
  <source>
   [javac] org\apache\tools\ant\listener\Log4jListener.java added as 
           \build\classes\org\apache\tools\ant\listener\Log4jListener.class 
               is outdated.
   [javac] org\apache\tools\ant\Location.java omitted as 
           \build\classes\org\apache\tools\ant\Location.class is up to date.
    ...
   [javac] Compiling 1 source file to \jakarta-ant\build\classes
   [javac] Using modern compiler
   [javac] Compilation args: -d \jakarta-ant\build\classes -classpath 
           \jakarta-ant\build\classes;F:\jdk1.3\lib\tools.jar;
           \Ant\lib\optional.jar;\Ant\lib\log4j.jar;
           \Ant\lib\junit.jar;\Ant\lib\jaxp.jar;
           \Ant\lib\crimson.jar;\Ant\lib\ant.jar 
           -sourcepath \jakarta-ant\src\main -g:none -O
      [javac] File to be compiled:
      \src\main\org\apache\tools\ant\listener\Log4jListener.java  
  </source>
  
              <p>
                In many cases Ant tasks are wrappers around OS commands or other java classes.
In debug mode, many
                of these tasks will print out the equivalent command line, as the &lt;javac&gt;
task above does. If 
                you are having a problem, it is often useful to run the command directly in
the same way Ant is doing 
                and see if the problem persists. The problem may lie in the command being
run by Ant, or in the way 
                the Ant task is running the command. You can also see the effect of changing
attribute values on the
                generated command line. This can help you to understand whether you are using
the correct attributes
                and values.
              </p>
        </subsection>
  
        <subsection name="Has it been fixed?">
          <p>
            After examining the debug output, you still believe that the problem you are having
may be 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="/builds/jakarta-ant/nightly/">Jakarta web site</a>. While
Ant nightly
            builds are typically quite stable and are used by <a href="/builds/gump/latest/">
            Gump</a> to build many other Jakarta projects, these builds should be treated
as experimental. You can 
            install and verify whether your problem has been fixed. 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="/builds/jakarta-ant/nightly/optional/">area</a>.
Note that even 
            this snapshot does not contain every optional task.
          </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://nagoya.apache.org/bugzilla/">Apache
Bug Database</a>.
            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 it has, 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>
        
        <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>
        
        <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>
        </subsection>
        
           
      </section>
      
    </body>
  </document>
  
  
  
  1.14      +2 -0      jakarta-ant/webpage/xdocs/stylesheets/project.xml
  
  Index: project.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-ant/webpage/xdocs/stylesheets/project.xml,v
  retrieving revision 1.13
  retrieving revision 1.14
  diff -u -r1.13 -r1.14
  --- project.xml	2001/07/04 11:42:19	1.13
  +++ project.xml	2001/08/06 13:37:08	1.14
  @@ -21,6 +21,8 @@
                 href="/resources.html"/>
           <item name="Ant FAQ"
                 href="/faq.html"/>
  +        <item name="Having Problems?"
  +              href="/problems.html"/>
       </menu>
   
       <menu name="Download">
  
  
  

Mime
View raw message