You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by fl...@apache.org on 2012/10/27 14:55:01 UTC

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

Author: florent
Date: Sat Oct 27 12:55:01 2012
New Revision: 1402794

URL: http://svn.apache.org/viewvc?rev=1402794&view=rev
Log:
STANBOL-789 use code block on each line. No space preservation but rendreing is not so bad

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=1402794&r1=1402793&r2=1402794&view=diff
==============================================================================
--- stanbol/site/trunk/content/production/your-launcher.mdtext (original)
+++ stanbol/site/trunk/content/production/your-launcher.mdtext Sat Oct 27 12:55:01 2012
@@ -35,7 +35,7 @@ Stanbol launcher's use this bundlelist m
     * 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 :
+* 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 :
     * "The Apache Stanbol lauchpad" and "maven-launchpad-plugin builds on the launchpad.base app" : dependencies required for the launcher to launch
     * "OSGi Framemework Bundle List" : provide all bundle for the OSGI in Stanbol
     * "Stanbol Commons Bundle List" : contains all the feature's shared bundles 
@@ -43,7 +43,7 @@ Stanbol launcher's use this bundlelist m
     * "Stanbol Enhancer Bundle List" : will provide all required bundles for the enhancer feature
     * "Stanbol Entityhub Bundle List" : will provide the EntityHub feature
 
-* At the end, your <dependencies> section only contains this 7 dependencies.
+* At the end, your ```<dependencies>``` section only contains this 7 dependencies.
 * Do an "mvn clean install"
 * Move to you target folder and launch the my-launcher.jar.
 * You get a running Stanbol with only the features you need.
@@ -72,21 +72,19 @@ Stanbol launcher's use this bundlelist m
     * 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 :
 
-```
-    <bundles>
-        <startlevel level="L0">
-            <bundle>
-                ...Maven groupId,artifactID and version properties...
-            </bundle>
-            <bundle>
-                ...another Maven's dependency information...
-            </bundle>
-        </startlevel>
-        <startlevel level="L1">
-            ... anothers bundles nodes...
-        </startlevel>
-    </bundles>
-```
+```    <bundles>```  
+```        <startlevel level="L0">```  
+```            <bundle>```  
+```                ...Maven groupId,artifactID and version properties...```  
+```            </bundle>```  
+```            <bundle>```  
+```                ...another Maven's dependency information...```  
+```            </bundle>```  
+```        </startlevel>```  
+```        <startlevel level="L1">```  
+```            ... anothers bundles nodes...```  
+```        </startlevel>```  
+```    </bundles>```  
 
 
 * 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.
@@ -98,22 +96,19 @@ Stanbol launcher's use this bundlelist m
 
 * Let's says that your bundlelist pom.xml contains :  
 
-```
-    <groupId>com.example</groupId>
-    <artifactId>my.bundlelist</artifactId>
-    <version>0.10.0-SNAPSHOT</version>
-    <packaging>partialbundlelist</packaging>
-```
+```    <groupId>com.example</groupId>```  
+```    <artifactId>my.bundlelist</artifactId>```  
+```    <version>0.10.0-SNAPSHOT</version>```  
+```    <packaging>partialbundlelist</packaging>```  
+
 
 * Bring your bundles into your launcher only require you to edit my-launcher/pom.xml and add in <dependencies> section, this one :  
 
-```
-    <dependency>
-      <groupId>com.example</groupId>
-      <artifactId>my.bundlelist</artifactId>
-      <version>0.10.0-SNAPSHOT</version>
-      <packaging>partialbundlelist</packaging>
-    </dependency>
-```
+```    <dependency>```  
+```      <groupId>com.example</groupId>```  
+```      <artifactId>my.bundlelist</artifactId>```  
+```      <version>0.10.0-SNAPSHOT</version>```  
+```      <packaging>partialbundlelist</packaging>```  
+```    </dependency>```  
 
 * Stanbol is now all yours !