svn commit: r975798 - in /websites/staging/jena/trunk/content: ./ documentation/fuseki2/fuseki-configuration.html

[bu...@apache.org]

Author: buildbot
Date: Thu Dec 17 13:34:21 2015
New Revision: 975798

Log:
Staging update by buildbot for jena

Modified:
    websites/staging/jena/trunk/content/   (props changed)
    websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-configuration.html

Propchange: websites/staging/jena/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Dec 17 13:34:21 2015
@@ -1 +1 @@
-1720486
+1720547

Modified: websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-configuration.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-configuration.html (original)
+++ websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-configuration.html Thu Dec 17 13:34:21 2015
@@ -164,7 +164,7 @@ h2:hover > .headerlink, h3:hover > .head
 <li>The service configuration file.  For compatibility, the service configuration file can also have data services. <a href="#relationship-to-fuseki-1-configuration">See below</a>.</li>
 <li>The command line, if not running as a web application from a .war file.</li>
 </ol>
-<p><code>FUSEKI_BASE</code> is the location of the <a href="#fuseki-layout.html">Fuseki run area</a>.</p>
+<p><code>FUSEKI_BASE</code> is the location of the <a href="./fuseki-layout.html">Fuseki run area</a>.</p>
 <h2 id="data-service-assembler">Data Service assembler<a class="headerlink" href="#data-service-assembler" title="Permanent link">&para;</a></h2>
 <p>See <a href="fuseki-data-services.html">Fuseki Data Services</a> for the architecture of data services.</p>
 <p>See <a href="fuseki-security.html">Fuseki Security</a> for more information on security.</p>
@@ -289,7 +289,7 @@ web application and the additional class
 <p>Configurations from Fuseki 1, where all dataset and server setup is in a
 single configuration file, will still work.  It is less flexible
 (you can't restart these services after stopping them in a running server)
-and user should plan to migrate to the new layout.</p>
+and user should plan to migrate to the <a href="./fuseki-layout.html">new layout</a>.</p>
 <p>To convert a Fuseki 1 configuration setup to Fuseki 2 style, move each data service assembler and put in it's own file under <code>FUSEKI_BASE/configuration/</code></p>
   </div>
 </div>