Author: thorsten
Date: Mon Feb 13 16:29:05 2006
New Revision: 377547
URL: http://svn.apache.org/viewcvs?rev=377547&view=rev
Log:
Updated installing instructions to reflect current developement
Modified:
forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-structurer-install.xml
Modified:
forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-structurer-install.xml
URL:
http://svn.apache.org/viewcvs/forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-structurer-install.xml?rev=377547&r1=377546&r2=377547&view=diff
==============================================================================
---
forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-structurer-install.xml
(original)
+++
forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-structurer-install.xml
Mon Feb 13 16:29:05 2006
@@ -23,7 +23,7 @@
<abstract>
This How-To describes the setup of the plugins (needed to work with
forrest:views and forrest:contracts) and a fresh v2 seed site.
</abstract>
- <last-modified-content-date date="2005-10-04"/>
+ <last-modified-content-date date="2006-02-14"/>
</header>
<audience title="Intended Audience">
@@ -59,21 +59,18 @@
will become easier in the future.
</p>
<section id="localBuild">
- <title>Build the internal.structurer and the output.themer
plugins</title>
+ <title>Build the internal.dispatcher and the themes.core plugins</title>
<p>
- The first step is to build and deploy the internal.structurer and the
output.themer plugins.
+ The first step is to build and deploy the internal.dispatcher and the
themes.core plugins.
</p>
<p>
- Run the script <code>etc/structurer.sh</code> *after* you did an svn
update.
- </p>
- <p>
- Otherwise build and deploy them manually. Do your usual 'svn update',
then ...
+ Do your usual 'svn update' on forrest (build it clean and normal),
then ...
</p>
<source>
-cd whiteboard/plugins/org.apache.forrest.plugin.internal.structurer/
+cd whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/
$FORREST_HOME/tools/ant/bin/ant local-deploy
-cd ../org.apache.forrest.plugin.output.themer/
+cd ../org.apache.forrest.themes.core/
$FORREST_HOME/tools/ant/bin/ant local-deploy
</source>
</section>
@@ -82,34 +79,18 @@
<p> Go to the directory where you want to seed a new project and seed it
...
</p>
<source>cd ~/src/
-mkdir v2
-cd v2/
-forrest seed-v2 </source>
- <note>
- For the moment we will use a special seed template called seed-v2. We
still
- need to fix issues of the dispatcher, so that it really can replace
old
- fashion skins. Like performance, standalone contracts, other testing
output/input formats - using POJO based
- processing will help solving this. All this will happen in the v2
seed-target until the dispatcher will
- be released to the stable plugins. So make regular updates of your
forrest-trunk to keep track.
- </note>
- <warning>
- The way we develop contracts will/may change with introduction of
java-based processing
- (for certain parts) rather then xsl. Please keep this in mind
- and help updating the documentation by sending patches. TIA. ;-)
- </warning>
+mkdir dispatcher
+cd dispatcher/
+forrest seed </source>
</section>
<section id="forrestProperties">
<title>Modify forrest.properties</title>
<p>
- Make sure to tell forrest to use the dispatcher plugins. Of course, if
you are
- using "seed-v2" then this is already done. If you are converting an
existing site to use
- dispatcher, then do this.
- </p>
- <p>
+ Make sure to tell forrest to use the dispatcher plugins. <br/>
Edit forrest.properties to add the required plugins:
</p>
<source>
-project.required.plugins=org.apache.forrest.plugin.output.themer,org.apache.forrest.plugin.internal.structurer
+project.required.plugins=org.apache.forrest.themes.core,org.apache.forrest.plugin.internal.dispatcher
</source>
</section>
<section id="testing">
@@ -125,14 +106,11 @@
<title>Available contracts</title>
<p>
To start working with the dispatcher, you need to know which contracts
you can use.
- If you used the seed-v2 then the Samples tab will lead to
- the available contracts.</p>
- <p>
- Forrestbar is another way to see available contracts. See the menu
point "Devs"
+ Forrestbar is a nice way to see available contracts. See the menu point
"Devs"
(ls.contracts and/or ls.contracts.project)
</p><p>
- Now point your browser to e.g.
<code>http://localhost:8888/ls.contracts.html</code>
- ... On this page you will find all contracts that you can use in your
project.
+ You can point your browser to e.g.
<code>http://localhost:8888/ls.contracts.html</code>
+ ... On this page you will find all contracts that you can use in your
project provided by the core themes.
</p>
</section>
</steps>
