svn commit: r868876 - in /websites/staging/aries/trunk/content: ./ modules/esamavenpluginproject.html

[buildbot]

Author: buildbot
Date: Tue Jul  9 07:46:29 2013
New Revision: 868876

Log:
Staging update by buildbot for aries

Modified:
    websites/staging/aries/trunk/content/   (props changed)
    websites/staging/aries/trunk/content/modules/esamavenpluginproject.html

Propchange: websites/staging/aries/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Jul  9 07:46:29 2013
@@ -1 +1 @@
-1500769
+1501119

Modified: 
websites/staging/aries/trunk/content/modules/esamavenpluginproject.html
==============================================================================
--- websites/staging/aries/trunk/content/modules/esamavenpluginproject.html 
(original)
+++ websites/staging/aries/trunk/content/modules/esamavenpluginproject.html Tue 
Jul  9 07:46:29 2013
@@ -354,6 +354,34 @@ this:</p>
 <div class="codehilite"><pre><span class="nt">&lt;configuration&gt;</span>
   <span class="nt">&lt;archiveContent&gt;</span>subsystemContent<span 
class="nt">&lt;/archiveContent&gt;</span>
 <span class="nt">&lt;/configuration&gt;</span>
+</pre></div>
+
+
+<p><a name="ESAMavenPluginProject-StartOrder"></a></p>
+<h2 id="content-bundle-start-ordering">Content Bundle Start Ordering</h2>
+<p>By default, the Subsystem runtime can start content bundles in any order.  
The OSGi start level service is not applicable to subsystems.  You can 
therefore specify the start order of the bundles based on the order in which 
they're expressed as dependencies in the maven pom using the following:</p>
+<div class="codehilite"><pre><span class="nt">&lt;configuration&gt;</span>
+  <span class="nt">&lt;startOrder&gt;</span>dependencies<span 
class="nt">&lt;/startOrder&gt;</span>
+<span class="nt">&lt;/configuration&gt;</span>
+</pre></div>
+
+
+<p><a name="ESAMavenPluginProject-ExistingSUBSYSTEM.MF"></a></p>
+<h2 id="including-an-existing-subsystem-manifest">Including an Existing 
Subsystem manifest</h2>
+<p>If you don't wish to generate the Subsystem manifest based on the pom 
configuration, you can add an existing one as follows:</p>
+<div class="codehilite"><pre><span class="nt">&lt;configuration&gt;</span>
+  <span class="nt">&lt;subsystemManifestFile&gt;</span><span 
class="cp">${</span><span class="n">basedir</span><span 
class="cp">}</span>/src/main/resources/OSGI-INF/SUBSYSTEM.MF<span 
class="nt">&lt;/subsystemManifestFile&gt;</span>
+<span class="nt">&lt;/configuration&gt;</span>
+</pre></div>
+
+
+<p><a name="ESAMavenPluginProject-OtherHeaders"></a></p>
+<h2 id="including-other-headers">Including Other Headers</h2>
+<p>You can add any other headers in addition to those calculated from the pom 
configuration.  For example, the following specifies the Subsystem Use-Bundle 
header and sets the Subsystem-Type to be a feature:</p>
+<div class="codehilite"><pre><span class="nt">&lt;instructions&gt;</span>
+    <span 
class="nt">&lt;Use-Bundle&gt;</span>org.apache.aries.test.Bundle;version=1.0.0-SNAPSHOT<span
 class="nt">&lt;/Use-Bundle&gt;</span>
+    <span class="nt">&lt;Subsystem-Type&gt;</span>feature<span 
class="nt">&lt;/Subsystem-Type&gt;</span>
+<span class="nt">&lt;/instructions&gt;</span>
 </pre></div></div>
             <!-- Content -->
           </td>