forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r366040 - in /forrest/trunk: main/webapp/WEB-INF/cli.xconf site-author/content/xdocs/docs_0_80/faq.xml
Date Thu, 05 Jan 2006 01:04:20 GMT
Author: crossley
Date: Wed Jan  4 17:04:15 2006
New Revision: 366040

URL: http://svn.apache.org/viewcvs?rev=366040&view=rev
Log:
Reduce the "checksums" FAQ to point to existing discussion about cli.xconf
Add explanation to the core cli.xconf about relative/absolute path.

Modified:
    forrest/trunk/main/webapp/WEB-INF/cli.xconf
    forrest/trunk/site-author/content/xdocs/docs_0_80/faq.xml

Modified: forrest/trunk/main/webapp/WEB-INF/cli.xconf
URL: http://svn.apache.org/viewcvs/forrest/trunk/main/webapp/WEB-INF/cli.xconf?rev=366040&r1=366039&r2=366040&view=diff
==============================================================================
--- forrest/trunk/main/webapp/WEB-INF/cli.xconf (original)
+++ forrest/trunk/main/webapp/WEB-INF/cli.xconf Wed Jan  4 17:04:15 2006
@@ -82,6 +82,9 @@
        |  files will not be written if their checksum has not changed.
        |  This means that it will be easier to detect which files
        |  need to be uploaded to a server, using the timestamp.
+       |
+       |  The default path is relative to the core webapp directory.
+       |  An asolute path can be used.
        +-->
    <!--   <checksums-uri>build/work/checksums</checksums-uri>-->
 

Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/faq.xml
URL: http://svn.apache.org/viewcvs/forrest/trunk/site-author/content/xdocs/docs_0_80/faq.xml?rev=366040&r1=366039&r2=366040&view=diff
==============================================================================
--- forrest/trunk/site-author/content/xdocs/docs_0_80/faq.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_80/faq.xml Wed Jan  4 17:04:15 2006
@@ -766,31 +766,25 @@
         to a big savings for a site with thousands of files.
         </p>
         <p>
+          Another reason could be if you are not using the forrestbot to
+          deploy the generated site. Some tools depend on the "date-last-modified"
+          timestamp of the generated files.
+        </p>
+        <p>
         There was some discussion about this on the Forrest developer mailing
-        list.  An archive of these discussions can be found here:
+        list:
         <link href="http://marc.theaimsgroup.com/?l=forrest-dev&amp;s=cocoon+checksum">Cocoon
Checksum</link> 
         Specifically note that this feature only stops Cocoon from writing to 
-        disk that which is the same as the existing file.  Cocoon still spends
+        disk if the new file is the same as the existing file.  Cocoon still spends
         the same amount of time generating the content as it would if checksums
         were not enabled.
         </p>
         <p>
-        There are two steps required to enable checksums within Cocoon and 
-        Forrest.  The first is to add this line to your forrest.properties
-        file: 
-        <code>project.configfile=${project.home}/src/documentation/conf/cli.xconf</code>
-        </p>
-        <p>
-        The second is to copy a template of this file from the Forrest
-        tree under <code>main/site-author/conf/cli.xconf</code> to the
-        <code>src/documentation/conf</code> directory.
-        </p>
-        <p>
-        An optional last step is to edit the cli.xconf file to specify
-        the directory where the checksums file will be stored.  By default this
-        file is stored in the forrest tree and not in your site's tree. 
         Locate the <code>checksums-uri</code> tag within cli.xconf and replace
         the contents with an absolute path and filename for the checksums file.
+        Projects can supply their own (see FAQ:
+        <link href="#cli-xconf">Cocoon cli.xconf</link>) or use the default
+        installation-wide cli.xconf file.
         </p>
       </answer>
     </faq>



Mime
View raw message