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

[fl...@apache.org]

Author: florent
Date: Sat Oct 27 12:45:17 2012
New Revision: 1402792

URL: http://svn.apache.org/viewvc?rev=1402792&view=rev
Log:
STANBOL-789 try the 4 spaces technic

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=1402792&r1=1402791&r2=1402792&view=diff
==============================================================================
--- stanbol/site/trunk/content/production/your-launcher.mdtext (original)
+++ stanbol/site/trunk/content/production/your-launcher.mdtext Sat Oct 27 12:45:17 2012
@@ -16,8 +16,6 @@ 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 :  
 
-```
-<pre>
     <dependency>
       <groupId>org.apache.stanbol</groupId>
       <artifactId>org.apache.stanbol.entityhub.bundlelist</artifactId>
@@ -25,8 +23,6 @@ Stanbol launcher's use this bundlelist m
       <type>partialbundlelist</type>
       <scope>provided</scope>
     </dependency>
-</pre>
-```
 
 * 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