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

[fl...@apache.org]

Author: florent
Date: Sat Oct 27 12:28:57 2012
New Revision: 1402788

URL: http://svn.apache.org/viewvc?rev=1402788&view=rev
Log:
STANBOL-789 try to restore the build

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=1402788&r1=1402787&r2=1402788&view=diff
==============================================================================
--- stanbol/site/trunk/content/production/your-launcher.mdtext (original)
+++ stanbol/site/trunk/content/production/your-launcher.mdtext Sat Oct 27 12:28:57 2012
@@ -16,7 +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 :  
 
-<code>
 ```
     <dependency>
       <groupId>org.apache.stanbol</groupId>
@@ -26,7 +25,7 @@ Stanbol launcher's use this bundlelist m
       <scope>provided</scope>
     </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
 
@@ -60,7 +59,7 @@ 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 :
-<code>
+
 ```
     mybundlelistFolder
       |
@@ -70,12 +69,11 @@ Stanbol launcher's use this bundlelist m
               |- bundles
                    |- list.xml
 ```
-</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 :
-<code>
+
 ```
     <bundles>
         <startlevel level="L0">
@@ -91,7 +89,7 @@ Stanbol launcher's use this bundlelist m
         </startlevel>
     </bundles>
 ```
-</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.
@@ -102,18 +100,15 @@ Stanbol launcher's use this bundlelist m
 
 * 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>
 ```
-</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>
@@ -122,6 +117,5 @@ Stanbol launcher's use this bundlelist m
       <packaging>partialbundlelist</packaging>
     </dependency>
 ```
-</code>
 
 * Stanbol is now all yours !