svn commit: r1402147 - /stanbol/site/trunk/content/production/your-launcher.mdtext

[fl...@apache.org]

Author: florent
Date: Thu Oct 25 13:35:33 2012
New Revision: 1402147

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

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

Modified: stanbol/site/trunk/content/production/your-launcher.mdtext
URL: http://svn.apache.org/viewvc/stanbol/site/trunk/content/production/your-launcher.mdtext?rev=1402147&r1=1402146&r2=1402147&view=diff
==============================================================================
--- stanbol/site/trunk/content/production/your-launcher.mdtext (original)
+++ stanbol/site/trunk/content/production/your-launcher.mdtext Thu Oct 25 13:35:33 2012
@@ -14,7 +14,8 @@ Stanbol launcher's use this bundlelist m
 ## Dependencies to bundlelist
 
 * 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 :
+* For example, if you want the entityHub feature in you server, you only need to add this dependency to your launcher pom.xml :  
+
 <code>
 ```
     <dependency>
@@ -25,8 +26,8 @@ Stanbol launcher's use this bundlelist m
       <scope>provided</scope>
     </dependency>
 ```
-<code>
-* Please note the ```xml<type>partialbundlelist</type>``` property of the dependency.
+</code>
+* Please note the ```<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
@@ -34,7 +35,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 ```xml <artifactId>org.apache.stanbol.launchers.full</artifactId>``` node to ```xml<artifactId>my.launcher</artifactId>```
+    * open the my-launcher/pom.xml and change the ```<artifactId>org.apache.stanbol.launchers.full</artifactId>``` node to ```<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 :
@@ -59,7 +60,8 @@ Stanbol launcher's use this bundlelist m
 ## Build *your* bundlelist dependency
 
 * Bundlelist (or partialbundlelist) artifact is a really simple Maven project that rely on this structure :
-<pre>
+<code>
+```
     mybundlelistFolder
       |
       |- pom.xml
@@ -67,12 +69,14 @@ Stanbol launcher's use this bundlelist m
           |- main
               |- bundles
                    |- list.xml
-</pre>
+```
+</code>
 
 * You only need to define 2 files : 
     * pom.xml : really simple you can copy-paste the [Enhancer bundlelist](http://svn.apache.org/repos/asf/stanbol/trunk/enhancer/bundlelist/pom.xml) one and only change the groupId and artifactId properties to suit you need. All the magic here is contained in <packaging> property.
     * list.xml : this file will contains information about the bundles you want to include. This file has a simple structure :
-<pre><code>
+<code>
+```
     <bundles>
         <startlevel level="L0">
             <bundle>
@@ -86,7 +90,8 @@ Stanbol launcher's use this bundlelist m
             ... anothers bundles nodes...
         </startlevel>
     </bundles>
-<code></pre>
+```
+</code>
 
 * Start level is an important things to keep in mind as the value of the "level" property will determine when your bundle is started during the server launch.
     * So, if your bundle require some other services to be up and running, be sure to define a higher start level to your bundle that the ones of the required services.
@@ -95,20 +100,28 @@ Stanbol launcher's use this bundlelist m
 
 ## Add *your* bundlelist to *your* launcher
 
-* Let's says that your bundlelist pom.xml contains :
-<pre>
+* Let's says that your bundlelist pom.xml contains :  
+
+<code>
+```
     <groupId>com.example</groupId>
     <artifactId>my.bundlelist</artifactId>
     <version>0.10.0-SNAPSHOT</version>
     <packaging>partialbundlelist</packaging>
-</pre>
-* Bring your bundles into your launcher only require you to edit my-launcher/pom.xml and add in <dependencies> section, this one : 
-<pre>
+```
+</code>
+
+* Bring your bundles into your launcher only require you to edit my-launcher/pom.xml and add in <dependencies> section, this one :  
+
+<code>
+```
     <dependency>
       <groupId>com.example</groupId>
       <artifactId>my.bundlelist</artifactId>
       <version>0.10.0-SNAPSHOT</version>
       <packaging>partialbundlelist</packaging>
     </dependency>
-</pre>
+```
+</code>
+
 * Stanbol is now all yours !