You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by mp...@apache.org on 2003/02/03 16:17:48 UTC
cvs commit: xml-forrest/src/documentation/content/xdocs forrestbot.xml
mpo 2003/02/03 07:17:47
Modified: src/documentation/content/xdocs forrestbot.xml
Log:
updated old documentation on the forrestbot to reflect the reality.
Revision Changes Path
1.9 +14 -10 xml-forrest/src/documentation/content/xdocs/forrestbot.xml
Index: forrestbot.xml
===================================================================
RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/forrestbot.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- forrestbot.xml 13 Jan 2003 10:19:18 -0000 1.8
+++ forrestbot.xml 3 Feb 2003 15:17:47 -0000 1.9
@@ -38,7 +38,7 @@
to yet another machine.</p>
<p>Running the bot is as easy as calling the following in your shell.
(executed in the root dir of the distribution.)</p>
- <source>build bot -Dbot.forrestbot.xconf=myOwn.conf.xml -Dtemplate.echo=[true|false]</source>
+ <source>build bot -Dbot.config=myOwn.conf.xml -Dtemplate.echo=[true|false]</source>
<p>It is quite typical to perform this from a shell script that gets
scheduled for execution on a regular basis.</p>
</section>
@@ -51,7 +51,7 @@
property. (if not specified with <code>-Dbot.forrest.xconf</code>
then the default config from the
distribution is taken: <code>./forrestbot.conf.xml</code>) </p>
- <p>This configuration file has one (optional) child-element for
+ <p>This configuration file has one (required, but optionally empty) child-element for
setting cross-project defaults, followed by a list of
project-elements that hold the configuration for the various projects
that the bot is going to work on.</p>
@@ -119,7 +119,8 @@
<user name="anoncvs"/>
<passwd name="anoncvs"/>
<module name="xml-forrest"/>
- <dir name="src/documentation"/>
+ <content-dir name="src/documentation"/>
+ <project-dir name=""/>
</get-src>
<generate>
@@ -147,28 +148,31 @@
<dd>forrest-site</dd>
</dl>
<dl>
- <dt>get.cvs.host</dt>
+ <dt>get-src.cvs.host</dt>
<dd>cvs.apache.org</dd>
</dl>
<dl>
- <dt>get.cvs.root</dt>
+ <dt>get-src.cvs.root</dt>
<dd>/home/cvspublic</dd>
</dl>
<dl>
- <dt>get.cvs.user</dt>
+ <dt>get-src.cvs.user</dt>
<dd>anoncvs</dd>
</dl>
<dl>
- <dt>passwd</dt>
+ <dt>get-src.cvs.passwd</dt>
<dd>anoncvs</dd>
</dl>
<dl>
- <dt>get.cvs.module</dt>
+ <dt>get-src.cvs.module</dt>
<dd>xml-forrest</dd>
</dl>
<dl>
- <dt>get.cvs.dir</dt>
+ <dt>get-src.cvs.content-dir</dt>
<dd>src/documentation</dd>
+ </dl><dl>
+ <dt>get-src.cvs.project-dir</dt>
+ <dd></dd>
</dl>
<dl>
<dt>generate.debuglevel</dt>
@@ -321,7 +325,7 @@
<li><code><destination></code> @name holds the path to the directory on the remote host where the generated content needs to be published. The process is using the <code>ftp cd</code> command to get there. This means this directory has to exist.</li>
</ul>
</section>
- <warning>Currently the ant distribution that is included in forrest cvs is not offering the required NetComponents.jar to actually support this type of deployment. If you want to use it anyway you should use get the required jar from <link href="http://www.savarese.org/oro/downloads/index.html#NetComponents">http://www.savarese.org/oro/downloads</link> and drop that into your <code>{forrest-sandbox}/tools/antipede/lib</code> directory. </warning>
+ <warning>Currently the ant distribution that is included in forrest cvs is not offering the required NetComponents.jar to actually support this type of deployment. If you want to use it anyway you should get the required jar from <link href="http://www.savarese.org/oro/downloads/index.html#NetComponents">http://www.savarese.org/oro/downloads</link> and drop that into your <code>{forrest-sandbox}/tools/antipede/lib</code> directory. </warning>
</section>
<section>
<title>