svn commit: r390566 - /forrest/trunk/site-author/content/xdocs/pluginDocs/plugins_0_80/usingPlugins.xml

[cr...@apache.org]

Author: crossley
Date: Fri Mar 31 17:44:54 2006
New Revision: 390566

URL: http://svn.apache.org/viewcvs?rev=390566&view=rev
Log:
Fix xml validation errors. <p> cannot contain <source>

Modified:
    forrest/trunk/site-author/content/xdocs/pluginDocs/plugins_0_80/usingPlugins.xml

Modified: forrest/trunk/site-author/content/xdocs/pluginDocs/plugins_0_80/usingPlugins.xml
URL: http://svn.apache.org/viewcvs/forrest/trunk/site-author/content/xdocs/pluginDocs/plugins_0_80/usingPlugins.xml?rev=390566&r1=390565&r2=390566&view=diff
==============================================================================
--- forrest/trunk/site-author/content/xdocs/pluginDocs/plugins_0_80/usingPlugins.xml (original)
+++ forrest/trunk/site-author/content/xdocs/pluginDocs/plugins_0_80/usingPlugins.xml Fri Mar 31 17:44:54 2006
@@ -50,8 +50,9 @@
            in the projects <code>forrest.properties</code> file. When Forrest 
            builds the site it will automatically discover the plugins and install 
            them. In otherwords, the user needs do nothing.</p>
-           <p>For example, 
+           <p>For example,</p>
            <source>project.required.plugins=org.apache.forrest.plugin.input.OpenOffice.org,org.apache.forrest.plugin.input.simplifiedDocbook</source>
+           <p>
            will cause Forrest to load the plugins called "org.apache.forrest.plugin.input.OpenOffice.org" and
            "org.apache.forrest.plugin.input.simplifiedDocbook".</p>
            <note>By default a new forrest project has that property configured
@@ -79,7 +80,9 @@
           <p>By default, forrest looks into the two following directories to find plugins sources : <code>${forrest.home}/plugins</code> and <code>${forrest.home}/whiteboard/plugins</code>.
           It is possible to add other sources locations by specifying the <code>project.required.plugins.src</code> property 
           in the projects <code>forrest.properties</code> file.</p>
-          <p>For example, <source>project.required.plugins.src=${forrest.home}/plugins,${forrest.home}/whiteboard/plugins,${project.home}/plugins</source>
+          <p>For example,</p>
+          <source>project.required.plugins.src=${forrest.home}/plugins,${forrest.home}/whiteboard/plugins,${project.home}/plugins</source>
+           <p>
            will add the project specific directory <code>${project.home}/plugins</code> to the list of directories to search in.</p>
           <p>if sources are not found, forrest will try to get them from the Web. Forrest <em>knows</em> the plugins description with plugins descriptors files 
           in which plugins are described as follows :</p>
@@ -98,7 +101,9 @@
           <p>By default, forrest gets the two following plugins descriptors files : <code>http://forrest.apache.org/plugins/plugins.xml</code> and <code>http://forrest.apache.org/plugins/whiteboard-plugins.xml</code>.
           It is possible to add other plugins descriptors files by specifying the <code>forrest.plugins.descriptors</code> property 
           in the projects <code>forrest.properties</code> file.</p>
-          <p>For example, <source>forrest.plugins.descriptors=http://forrest.apache.org/plugins/plugins.xml,http://forrest.apache.org/plugins/whiteboard-plugins.xml,file:///${project.home}/plugins/plugins.xml</source>
+          <p>For example,</p>
+          <source>forrest.plugins.descriptors=http://forrest.apache.org/plugins/plugins.xml,http://forrest.apache.org/plugins/whiteboard-plugins.xml,file:///${project.home}/plugins/plugins.xml</source>
+          <p>
           will add the project specific plugins descriptors file <code>file:///${project.home}/plugins/plugins.xml</code> to the list of descriptors.</p>
         </section>
       <section>