svn commit: r836135 - in /websites/staging/stanbol/trunk/content: ./ production/partial-updates.html production/your-launcher.html

[bu...@apache.org]

Author: buildbot
Date: Thu Oct 25 12:23:30 2012
New Revision: 836135

Log:
Staging update by buildbot for stanbol

Modified:
    websites/staging/stanbol/trunk/content/   (props changed)
    websites/staging/stanbol/trunk/content/production/partial-updates.html
    websites/staging/stanbol/trunk/content/production/your-launcher.html

Propchange: websites/staging/stanbol/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Oct 25 12:23:30 2012
@@ -1 +1 @@
-1402126
+1402127

Modified: websites/staging/stanbol/trunk/content/production/partial-updates.html
==============================================================================
--- websites/staging/stanbol/trunk/content/production/partial-updates.html (original)
+++ websites/staging/stanbol/trunk/content/production/partial-updates.html Thu Oct 25 12:23:30 2012
@@ -92,23 +92,11 @@ The Apache Sling File Provider allow you
 </p>
 <p>Follow this two step procedure to enjoy this feature :<br />
 </p>
-<ul>
-<li>
 <ol>
 <li>Install the "Sling File Provider" Bundle (not needed as this is included by default in Stanbol)</li>
-</ol>
-</li>
-<li>
-<ol>
 <li>Configure the "sling.fileinstall.dir" property: You can add this to the "{stanbol-working-dir}/stanbol/sling.properties file" or parse it as a system property '-Dsling.fileinstall.dir={path-to-dir}' when you start stanbol.</li>
-</ol>
-</li>
-<li>
-<ol>
 <li>Create the referenced Folder on you file system.</li>
 </ol>
-</li>
-</ul>
 <p>Note : this procedure was extracted for a Rupert Westenthaler's <a href="http://markmail.org/message/jpxpl6x4nkmz6kda">mail</a>. Thanks to him to spot it !</p>
   </div>
   

Modified: websites/staging/stanbol/trunk/content/production/your-launcher.html
==============================================================================
--- websites/staging/stanbol/trunk/content/production/your-launcher.html (original)
+++ websites/staging/stanbol/trunk/content/production/your-launcher.html Thu Oct 25 12:23:30 2012
@@ -97,8 +97,8 @@ But identify and manually add all featur
 <h2 id="dependencies-to-bundlelist">Dependencies to bundlelist</h2>
 <ul>
 <li>Bundlelist are in fact just jar. So you just need to declare them as dependencies in you launcher pom.xml to get the feature package and all required bundle for it.</li>
-<li>
-<p>For example, if you want the entityHub feature in you server, you only need to add this dependency to your launcher pom.xml :
+<li>For example, if you want the entityHub feature in you server, you only need to add this dependency to your launcher pom.xml :
+<code>
 <code>xml
     &lt;dependency&gt;
       &lt;groupId&gt;org.apache.stanbol&lt;/groupId&gt;
@@ -106,11 +106,9 @@ But identify and manually add all featur
       &lt;version&gt;0.11.0-SNAPSHOT&lt;/version&gt;
       &lt;type&gt;partialbundlelist&lt;/type&gt;
       &lt;scope&gt;provided&lt;/scope&gt;
-    &lt;/dependency&gt;</code></p>
-</li>
-<li>
-<p>Please note the <pre><type>partialbundlelist</type></pre> property of the dependency.</p>
-</li>
+    &lt;/dependency&gt;</code>
+<code></li>
+<li>Please note the <code>xml&lt;type&gt;partialbundlelist&lt;/type&gt;</code> property of the dependency.</li>
 <li>Also in actual Stanbol code base you can easily detect feature package bundlelist as their artifactId has the structure org.apache.stanbol.{feature-name}.bundlelist</li>
 </ul>
 <h2 id="build-your-launcher">Build <em>your</em> launcher</h2>
@@ -120,7 +118,7 @@ But identify and manually add all featur
 <p>The more simple way to get you custom launcher is to :</p>
 <ul>
 <li>copy the <a href="http://svn.apache.org/repos/asf/stanbol/trunk/launchers/full/">full launcher folder</a> to "my-launcher" folder</li>
-<li>open the my-launcher/pom.xml and change the <artifactId>org.apache.stanbol.launchers.full</artifactId> node to <artifactId>my.launcher</artifactId> </li>
+<li>open the my-launcher/pom.xml and change the <code>xml &lt;artifactId&gt;org.apache.stanbol.launchers.full&lt;/artifactId&gt;</code> node to <code>xml&lt;artifactId&gt;my.launcher&lt;/artifactId&gt;</code></li>
 </ul>
 </li>
 <li>