Author: buildbot
Date: Tue Oct 21 13:54:11 2014
New Revision: 926332
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 Oct 21 13:54:11 2014
@@ -1 +1 @@
-1631491
+1633381
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
Oct 21 13:54:11 2014
@@ -271,10 +271,10 @@
<!-- Content -->
<div class="wiki-content"><p><a
name="ESAMavenPluginProject-ESAMavenPlugin"></a></p>
<h1 id="esa-maven-plugin">ESA Maven Plugin</h1>
-<p>Note: the esa-maven-plugin has yet to be released and so to use it you must
first extract and build it from the Aries svn.</p>
+<p>This page describes the <code>esa-maven-plugin</code> version 1.0.0 which
is available from Maven Central.</p>
<p>The ESA Maven Plugin provides the ability to generate ESA archives using
Maven. The ESA archive format is defined in the Subsystems Service
Specification which was part of <a
href="http://www.osgi.org/Specifications/HomePage";>OSGi Enterprise R5</a>. An
ESA archive can optionally contain an Subsystem manifest
-(SUBSYSTEM.MF). This can be added in one of two ways</p>
+(<code>SUBSYSTEM.MF</code>). This can be added in one of two ways</p>
<ol>
<li>Hand written and added into the archive.</li>
<li>Generated based on pom configuration.</li>
@@ -282,49 +282,73 @@ Maven. The ESA archive format is define
<p><a name="ESAMavenPluginProject-UsingthePlugin"></a></p>
<h2 id="using-the-plugin">Using the Plugin</h2>
<p>The plugin is included by as follows:</p>
-<div class="codehilite"><pre> <span class="nt"><build></span>
+<div class="codehilite"><pre><span class="nt"><project></span>
+ ...
+ <span class="nt"><packaging></span>esa<span
class="nt"></packaging></span> <span class="c"><!-- set packaging type
to esa --></span>
+
+ <span class="nt"><build></span>
<span class="nt"><plugins></span>
- <span class="nt"><plugin></span>
+ <span class="nt"><plugin></span>
<span class="nt"><groupId></span>org.apache.aries<span
class="nt"></groupId></span>
<span class="nt"><artifactId></span>esa-maven-plugin<span
class="nt"></artifactId></span>
- <span class="nt"></plugin></span>
+ <span class="nt"><version></span>1.0.0<span
class="nt"></version></span>
+ <span class="nt"><extensions></span>true<span
class="nt"></extensions></span>
+ <span class="nt"></plugin></span>
<span class="nt"></plugins></span>
- <span class="nt"></build></span>
+ <span class="nt"></build></span>
+<span class="nt"></project></span>
</pre></div>
<p>By default it will not generate a manifest, so in the above example it will
-attempt to copy a pre-defined SUBSYSTEM.MF from
-src/main/resources/META-INF. If that file does not exist, then no
+attempt to copy a pre-defined <code>SUBSYSTEM.MF</code> from
+<code>src/main/resources/META-INF</code>. If that file does not exist, then no
Subsystem manifest will be included.</p>
<p><a name="ESAMavenPluginProject-GeneratinganSUBSYSTEM.MF"></a></p>
<h2 id="generating-an-subsystemmf">Generating an SUBSYSTEM.MF</h2>
-<p>The following example shows how to get the plugin to generate an
-SUBSYSTEM.MF based on the pom configuration:</p>
-<div class="codehilite"><pre> <span class="nt"><build></span>
+<p>The following example <code>pom.xml</code> shows how to get the plugin to
generate an
+<code>SUBSYSTEM.MF</code> based on the pom configuration:</p>
+<div class="codehilite"><pre><span class="nt"><project></span>
+ <span class="nt"><modelVersion></span>4.0.0<span
class="nt"></modelVersion></span>
+
+ <span class="nt"><groupId></span>org.something<span
class="nt"></groupId></span>
+ <span class="nt"><artifactId></span>esa-maven-plugin-test<span
class="nt"></artifactId></span>
+ <span class="nt"><version></span>1.0.0-SNAPSHOT<span
class="nt"></version></span>
+ <span class="nt"><packaging></span>esa<span
class="nt"></packaging></span>
+
+ <span class="nt"><dependencies></span>
+ <span class="c"><!-- Put some dependencies in here --></span>
+ <span class="nt"></dependencies></span>
+
+ <span class="nt"><build></span>
<span class="nt"><plugins></span>
- <span class="nt"><plugin></span>
+ <span class="nt"><plugin></span>
<span class="nt"><groupId></span>org.apache.aries<span
class="nt"></groupId></span>
<span class="nt"><artifactId></span>esa-maven-plugin<span
class="nt"></artifactId></span>
+ <span class="nt"><version></span>1.0.0<span
class="nt"></version></span>
+ <span class="nt"><extensions></span>true<span
class="nt"></extensions></span>
<span class="nt"><configuration></span>
- <span class="nt"><generateManifest></span>true<span
class="nt"></generateManifest></span>
+ <span class="nt"><generateManifest></span>true<span
class="nt"></generateManifest></span>
<span class="nt"></configuration></span>
- <span class="nt"></plugin></span>
+ <span class="nt"></plugin></span>
<span class="nt"></plugins></span>
- <span class="nt"></build></span>
+ <span class="nt"></build></span>
+<span class="nt"></project></span>
</pre></div>
-<p>The pom to subsystem manfiest header mapping is as follows:
-<em> Pom <groupId/>.<artifactId/> -> Subsystem-SymbolicName
-</em> Pom <name/> -> Subsystem-Name
-<em> Pom <version/> -> Subsystem-Version (cleaned up for OSGi)
-</em> Pom <description/> -> Subsystem-Description
-* Pom <dependencies/> -> Subsystem-Content</p>
+<p>The pom to subsystem manfiest header mapping is as follows:</p>
+<ul>
+<li>Pom <groupId/>.<artifactId/> -> Subsystem-SymbolicName</li>
+<li>Pom <name/> -> Subsystem-Name</li>
+<li>Pom <version/> -> Subsystem-Version (cleaned up for OSGi)</li>
+<li>Pom <description/> -> Subsystem-Description</li>
+<li>Pom <dependencies/> -> Subsystem-Content</li>
+</ul>
<p><a name="ESAMavenPluginProject-OverridingSubsystem-SymbolicName"></a></p>
<h2 id="overriding-subsystem-symbolicname">Overriding
Subsystem-SymbolicName</h2>
<p>The subsystem symbolic name defaults to the
-${project.groupId}.${project.artifaceId}. The following shows how to override
+${project.groupId}.${project.artifactId}. The following shows how to override
this:</p>
<div class="codehilite"><pre><span class="nt"><configuration></span>
<span class="nt"><instructions></span>
@@ -352,14 +376,14 @@ this:</p>
<p>The following specifies the default of including only the direct
dependencies (assumes the subsystem contents and direct dependencies are the
same).</p>
<div class="codehilite"><pre><span class="nt"><configuration></span>
- <span class="nt"><archiveContent></span>subsystemContent<span
class="nt"></archiveContent></span>
+ <span class="nt"><archiveContent></span>content<span
class="nt"></archiveContent></span>
<span class="nt"></configuration></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>
+<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 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"><configuration></span>
<span class="nt"><startOrder></span>dependencies<span
class="nt"></startOrder></span>
<span class="nt"></configuration></span>
