Author: kwright
Date: Mon Nov 22 18:51:27 2010
New Revision: 1037835
URL: http://svn.apache.org/viewvc?rev=1037835&view=rev
Log:
Promote javadoc, etc to the main navigation area.
Modified:
incubator/lcf/trunk/site/src/documentation/content/xdocs/developer-resources.xml
incubator/lcf/trunk/site/src/documentation/content/xdocs/how-to-build-and-deploy.xml
incubator/lcf/trunk/site/src/documentation/content/xdocs/site.xml
Modified: incubator/lcf/trunk/site/src/documentation/content/xdocs/developer-resources.xml
URL: http://svn.apache.org/viewvc/incubator/lcf/trunk/site/src/documentation/content/xdocs/developer-resources.xml?rev=1037835&r1=1037834&r2=1037835&view=diff
==============================================================================
--- incubator/lcf/trunk/site/src/documentation/content/xdocs/developer-resources.xml (original)
+++ incubator/lcf/trunk/site/src/documentation/content/xdocs/developer-resources.xml Mon Nov 22 18:51:27 2010
@@ -14,30 +14,6 @@
</p>
</section>
- <section id="understandingManifoldCF">
- <title>Familiarize Yourself with the Concepts and Terminology</title>
- <p>Like any software project, ManifoldCF has its own underlying concepts and terminology. Read about that <a href="concepts.html">here</a>.
- </p>
- </section>
-
- <section id="interoperability">
- <title>Interoperability Matrix</title>
- <p>The interoperability and testing matrix for ManifoldCF can be found <a href="included-connectors.html">here</a>.
- </p>
- </section>
-
- <section id="howtobuilddeploy">
- <title>How to Build and Deploy</title>
- <p>Building ManifoldCF requires ant 1.7 or greater. Instructions for building and deploying can be found <a href="how-to-build-and-deploy.html">here</a>.
- </p>
- </section>
-
- <section id="howtointegrate">
- <title>How to Integrate</title>
- <p>ManifoldCF provides a number of API's and services. Documentation of these API's can be found <a href="programmatic-operation.html">here</a>.
- </p>
- </section>
-
<section id="securityarchitecturediagrams">
<title>Security Architecture Diagrams</title>
<p>For those who prefer a pictorial representation of ManifoldCF's security architecture, this might help.</p>
@@ -63,7 +39,6 @@
<p>Writing connectors for ManifoldCF is a great way to learn about the project and contribute something useful! Read about how to do that by navigating to the links provided below.
</p>
<ul>
- <li><a href="javadoc.html">ManifoldCF Javadoc</a></li>
<li><a href="writing-output-connectors.html">How to write an output connector</a></li>
<li><a href="writing-authority-connectors.html">How to write an authority connector</a></li>
<li><a href="writing-repository-connectors.html">How to write a repository connector</a></li>
Modified: incubator/lcf/trunk/site/src/documentation/content/xdocs/how-to-build-and-deploy.xml
URL: http://svn.apache.org/viewvc/incubator/lcf/trunk/site/src/documentation/content/xdocs/how-to-build-and-deploy.xml?rev=1037835&r1=1037834&r2=1037835&view=diff
==============================================================================
--- incubator/lcf/trunk/site/src/documentation/content/xdocs/how-to-build-and-deploy.xml (original)
+++ incubator/lcf/trunk/site/src/documentation/content/xdocs/how-to-build-and-deploy.xml Mon Nov 22 18:51:27 2010
@@ -562,7 +562,7 @@ log4j.appender.MAIN.layout.ConversionPat
<tr><td>FileNet</td><td>filenet-registry-process</td><td>org.apache.manifoldcf.crawler.registry.filenet.Filenet</td><td>filenet-registry-process/script/run[.sh|.bat]</td></tr>
</table>
<p>The registry process in all cases must be started before the corresponding server process, or the server process will report an error. (It will, however, retry after some period of time.) The scripts all require an MCF_HOME environment variable pointing to the place where properties.xml is found, as well as a JAVA_HOME environment variable pointing the JDK. The server scripts also require other environment variables as well, consistent with the needs of the DFC or the FileNet API respectively. For example, DFC requires the DOCUMENTUM environment variable to be set, while the FileNet server script requires the WASP_HOME environment variable.</p>
- <p>It is important to understand that the scripts work by building a classpath out of all jars that get copied into the <em>jar</em> directory underneath each process during the ant build. These jars come in part from the <em>dfc></em> or <em>filenet-api</em> directories underneath the documentum or filenet connector directories. For the server startup scripts to work properly, therefore, these directories should have <strong>all</strong> of the jars needed to allow the api code to function, and the ant build scripts will take care of the rest.</p>
+ <p>It is important to understand that the scripts work by building a classpath out of all jars that get copied into the <em>jar</em> directory underneath each process during the ant build. These jars come in part from the <em>dfc</em> or <em>filenet-api</em> directories underneath the documentum or filenet connector directories. For the server startup scripts to work properly, therefore, these directories should have <strong>all</strong> of the jars needed to allow the api code to function, and the ant build scripts will take care of the rest.</p>
<p></p>
</section>
</section>
Modified: incubator/lcf/trunk/site/src/documentation/content/xdocs/site.xml
URL: http://svn.apache.org/viewvc/incubator/lcf/trunk/site/src/documentation/content/xdocs/site.xml?rev=1037835&r1=1037834&r2=1037835&view=diff
==============================================================================
--- incubator/lcf/trunk/site/src/documentation/content/xdocs/site.xml (original)
+++ incubator/lcf/trunk/site/src/documentation/content/xdocs/site.xml Mon Nov 22 18:51:27 2010
@@ -26,7 +26,12 @@
<thanks label="Sponsors of Apache" href="ext:thanks" />
</project>
<docs label="Documentation">
+ <dev label="Concepts" href="concepts.html"/>
+ <dev lable="Compatibility Matrix" href="included-connectors.html"/>
<dev label="Frequently Asked Questions" href="faq.html"/>
+ <dev label="API Documentation" href="programmatic-operation.html"/>
+ <dev label="Javadoc" href="javadoc.html"/>
+ <dev label="Building and Deploying" href="how-to-build-and-deploy.html"/>
<dev label="Developer/Integrator Resources" href="developer-resources.html"/>
<dev label="End-user Documentation" href="end-user-documentation.html"/>
</docs>