svn commit: r1402127 - in /stanbol/site/trunk/content/production: partial-updates.mdtext your-launcher.mdtext

[fl...@apache.org]

Author: florent
Date: Thu Oct 25 12:23:26 2012
New Revision: 1402127

URL: http://svn.apache.org/viewvc?rev=1402127&view=rev
Log:
STANBOL-789 md format, another try

Modified:
    stanbol/site/trunk/content/production/partial-updates.mdtext
    stanbol/site/trunk/content/production/your-launcher.mdtext

Modified: stanbol/site/trunk/content/production/partial-updates.mdtext
URL: http://svn.apache.org/viewvc/stanbol/site/trunk/content/production/partial-updates.mdtext?rev=1402127&r1=1402126&r2=1402127&view=diff
==============================================================================
--- stanbol/site/trunk/content/production/partial-updates.mdtext (original)
+++ stanbol/site/trunk/content/production/partial-updates.mdtext Thu Oct 25 12:23:26 2012
@@ -6,8 +6,8 @@ The Apache Sling File Provider allow you
 
 Follow this two step procedure to enjoy this feature :  
 
-* 0. Install the "Sling File Provider" Bundle (not needed as this is included by default in Stanbol)
-* 1. 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.
-* 2. Create the referenced Folder on you file system.
+0. Install the "Sling File Provider" Bundle (not needed as this is included by default in Stanbol)
+1. 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.
+2. Create the referenced Folder on you file system.
 
 Note : this procedure was extracted for a Rupert Westenthaler's [mail](http://markmail.org/message/jpxpl6x4nkmz6kda). Thanks to him to spot it !

Modified: stanbol/site/trunk/content/production/your-launcher.mdtext
URL: http://svn.apache.org/viewvc/stanbol/site/trunk/content/production/your-launcher.mdtext?rev=1402127&r1=1402126&r2=1402127&view=diff
==============================================================================
--- stanbol/site/trunk/content/production/your-launcher.mdtext (original)
+++ stanbol/site/trunk/content/production/your-launcher.mdtext Thu Oct 25 12:23:26 2012
@@ -15,6 +15,7 @@ Stanbol launcher's use this bundlelist m
 
 * 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.
 * For example, if you want the entityHub feature in you server, you only need to add this dependency to your launcher pom.xml :
+<code>
 ```xml
     <dependency>
       <groupId>org.apache.stanbol</groupId>
@@ -24,8 +25,8 @@ Stanbol launcher's use this bundlelist m
       <scope>provided</scope>
     </dependency>
 ```
-
-* Please note the <pre><type>partialbundlelist</type></pre> property of the dependency.
+<code>
+* Please note the ```xml<type>partialbundlelist</type>``` property of the dependency.
 * 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
 
 ## Build *your* launcher
@@ -33,7 +34,7 @@ Stanbol launcher's use this bundlelist m
 * Let's imagine that for now you only use EntityHub and Enhancer features packages.
 * The more simple way to get you custom launcher is to :
     * copy the [full launcher folder](http://svn.apache.org/repos/asf/stanbol/trunk/launchers/full/) to "my-launcher" folder
-    * open the my-launcher/pom.xml and change the <artifactId>org.apache.stanbol.launchers.full</artifactId> node to <artifactId>my.launcher</artifactId> 
+    * open the my-launcher/pom.xml and change the ```xml <artifactId>org.apache.stanbol.launchers.full</artifactId>``` node to ```xml<artifactId>my.launcher</artifactId>```
 
 * Then you get a custom launcher, but still with all the Stanbol features.
 * To only keep the features you want (EntityHub and Enhancer in this example), scroll down to the <dependencies> part and remove all **but** dependencies labelled with :