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/etc RELEASE-NOTES-0.2.txt
Date Wed, 13 Nov 2002 09:24:29 GMT
crossley    2002/11/13 01:24:29

  Modified:    etc      RELEASE-NOTES-0.2.txt
  Log:
  Polishing by The Cleaning Lady.
  
  Revision  Changes    Path
  1.2       +14 -14    xml-forrest/etc/RELEASE-NOTES-0.2.txt
  
  Index: RELEASE-NOTES-0.2.txt
  ===================================================================
  RCS file: /home/cvs/xml-forrest/etc/RELEASE-NOTES-0.2.txt,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- RELEASE-NOTES-0.2.txt	12 Nov 2002 16:12:24 -0000	1.1
  +++ RELEASE-NOTES-0.2.txt	13 Nov 2002 09:24:29 -0000	1.2
  @@ -11,7 +11,7 @@
   
   This document describes the 0.2 release of Apache Forrest, how to get started,
   known bugs and any other issues.  Please send all feedback to
  -forrest-dev@xml.apache.org.
  +forrest-dev@xml.apache.org
   
   2)  Status
   ----------
  @@ -19,7 +19,7 @@
   (including xml.apache.org).  However, forrest-dev explicitly DOES NOT intend to
   maintain the degree of accountability and backwards-compatibility intended for
   future 0.x releases.  This 0.2 release is made primarily to meet user demand,
  -to solicit feedback, and to give the Forrest community a trail run in the
  +to solicit feedback, and to give the Forrest community a trial run in the
   process of Forrest releases.
   
   
  @@ -30,7 +30,7 @@
   Apache Cocoon, providing XSLT stylesheets and schemas, images and other
   resources. Forrest uses these to render the XML source content into a website
   via command-line, robot, or a dynamic web application.  For more details,
  -please see the website, http://xml.apache.org/forrest/.
  +please see the website at http://xml.apache.org/forrest/
   
   4) Requirements
   ---------------
  @@ -43,7 +43,7 @@
     higher) to build, obtainable from the same URL.
   
   Ant is not required: Forrest uses its own stripped-down, souped-up Ant in
  -tools/ant/.
  +tools/ant/
   
   
   5) Installing Forrest
  @@ -65,9 +65,9 @@
   
       (if Ant 1.5+ is installed, typing 'ant' works just as well)
   
  -    A binary distribution should be built in build/dist/shbat.  Add the path to
  -    build/dist/shbat/bin to your PATH environment variable, and you have
  -    Forrest installed.
  +    A binary distribution will be built in build/dist/shbat
  +    Add the path to build/dist/shbat/bin to your PATH environment variable,
  +    and you have Forrest installed.
   
   o 5.2) Binary distribution
     ------------------------
  @@ -92,9 +92,9 @@
    - Type 'forrest -projecthelp'.  This should list the available Forrest
      commands.
   
  - - Create an empty directory somewhere, and enter it.
  + - Create an empty directory somewhere, and change cd to it.
   
  -   [ Eg: mkdir /tmp/mysite ; cd /tmp/mysite ]
  +   [ e.g. mkdir /tmp/mysite ; cd /tmp/mysite ]
   
    - Type 'forrest seed'.  This will create a template site in the current
      directory, ready for you to edit or render.
  @@ -102,7 +102,7 @@
    - (optional) Edit the XML content in src/documentation/content/xdocs
      Have a look around, familiarize yourself with the structure.
   
  - - In your new project root [Eg: /tmp/mysite],  type 'forrest validate'.
  + - In your new project root [ e.g. /tmp/mysite ],  type 'forrest validate'.
      This will check that all XML files are valid.  Actually Forrest does this
      automatically for the next step, but we're proud of our validation :)
   
  @@ -130,9 +130,9 @@
    7.2)
      When running a Forrest site as a webapp, a user reports:
   
  -   "When I call a page for 2ond time, it should be cached.  But as we can see
  +   "When I call a page for second time, it should be cached.  But as we can see
      in the logs attached, it is not, although the 3 aggregated xml (book, tabs
  -   and body, are cached).
  +   and body) are cached.
   
      Another problem is the evaluation of the xslt just before the cache
      validation. In the documents is too much time consuming, as you can see in
  
  
  

Mime
View raw message