Author: gcc
Date: Tue Jul 9 07:46:14 2013
New Revision: 1501119
URL: http://svn.apache.org/r1501119
Log:
Updates to esa-maven-plugin docs
Modified:
aries/site/trunk/content/modules/esamavenpluginproject.mdtext
Modified: aries/site/trunk/content/modules/esamavenpluginproject.mdtext
URL:
http://svn.apache.org/viewvc/aries/site/trunk/content/modules/esamavenpluginproject.mdtext?rev=1501119&r1=1501118&r2=1501119&view=diff
==============================================================================
--- aries/site/trunk/content/modules/esamavenpluginproject.mdtext (original)
+++ aries/site/trunk/content/modules/esamavenpluginproject.mdtext Tue Jul 9
07:46:14 2013
@@ -111,3 +111,32 @@ The following specifies the default of i
<archiveContent>subsystemContent</archiveContent>
</configuration>
+<a name="ESAMavenPluginProject-StartOrder"></a>
+## Content Bundle Start Ordering
+
+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:
+
+ <configuration>
+ <startOrder>dependencies</startOrder>
+ </configuration>
+
+<a name="ESAMavenPluginProject-ExistingSUBSYSTEM.MF"></a>
+## Including an Existing Subsystem manifest
+
+If you don't wish to generate the Subsystem manifest based on the pom
configuration, you can add an existing one as follows:
+
+ <configuration>
+
<subsystemManifestFile>${basedir}/src/main/resources/OSGI-INF/SUBSYSTEM.MF</subsystemManifestFile>
+ </configuration>
+
+<a name="ESAMavenPluginProject-OtherHeaders"></a>
+## Including Other Headers
+
+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:
+
+ <instructions>
+
<Use-Bundle>org.apache.aries.test.Bundle;version=1.0.0-SNAPSHOT</Use-Bundle>
+ <Subsystem-Type>feature</Subsystem-Type>
+ </instructions>
+
+
