forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject cvs commit: xml-forrest/src/documentation/content/xdocs faq.xml
Date Wed, 31 Jul 2002 02:09:34 GMT
crossley    2002/07/30 19:09:34

  Modified:    .        status.xml
               src/documentation/content/xdocs faq.xml
  Log:
  Added item to FAQ and ToDo. Why need "build clean" before "build docs"?
  
  Revision  Changes    Path
  1.8       +5 -0      xml-forrest/status.xml
  
  Index: status.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/status.xml,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- status.xml	30 Jul 2002 01:36:16 -0000	1.7
  +++ status.xml	31 Jul 2002 02:09:34 -0000	1.8
  @@ -54,6 +54,11 @@
        of forrest.xgump, but the jar and Ant tasks remain. (See
        <link href="http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=102406503426469">Gumping
_Forrest_</link>)
       </action>
  +    <action context="code" dev="open">
  +     Why do we need to always use "build clean" before doing "build docs"?
  +     Perhaps something with the re-introduction of Jisp.
  +     See email discussion at <link href="http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=102767862102557">http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=102767862102557</link>
  +    </action>
       <action context="design" dev="open">
        Clarify the URL namespace architecture for Forrest and document it.
       </action>
  
  
  
  1.12      +15 -2     xml-forrest/src/documentation/content/xdocs/faq.xml
  
  Index: faq.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/faq.xml,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- faq.xml	26 Jul 2002 05:28:10 -0000	1.11
  +++ faq.xml	31 Jul 2002 02:09:34 -0000	1.12
  @@ -23,8 +23,9 @@
    <answer>
     <p>
      Run &quot;<code>./build.sh docs</code>&quot; to see the documentation
  -   for Forrest. Logfiles are generated in the <code>build/work/WEB-INF/logs/</code>
  -   directory.
  +   for Forrest.
  +   The documentation is generated in the <code>build/docs/</code> directory.
  +   Logfiles are in the <code>build/work/WEB-INF/logs/</code> directory.
     </p>
    </answer>
   </faq>
  @@ -60,6 +61,18 @@
      See the 
      <link href="todo.html">To Do List </link> and choose something that
      interests you.
  +  </p>
  + </answer>
  +</faq>
  +
  +<faq>
  + <question>
  +  Why is build docs failing on subsequent builds?
  + </question>
  + <answer>
  +  <p>
  +   It is a bug. Workaround: <code>./build.sh clean docs</code> every time.
  +   There is an entry on the <link href="todo.html">To Do List</link>.
     </p>
    </answer>
   </faq>
  
  
  

Mime
View raw message