Author: buildbot
Date: Fri Jul 3 09:17:06 2015
New Revision: 956802
Log:
Staging update by buildbot for aries
Modified:
websites/staging/aries/trunk/content/ (props changed)
websites/staging/aries/trunk/content/modules/subsystems.html
Propchange: websites/staging/aries/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Jul 3 09:17:06 2015
@@ -1 +1 @@
-1688860
+1688976
Modified: websites/staging/aries/trunk/content/modules/subsystems.html
==============================================================================
--- websites/staging/aries/trunk/content/modules/subsystems.html (original)
+++ websites/staging/aries/trunk/content/modules/subsystems.html Fri Jul 3
09:17:06 2015
@@ -98,7 +98,18 @@
<div id="wrapper-menu-page-bottom">
<div id="menu-page">
<!-- NavigationBar -->
- <div onclick="SwitchMenu('overview')" id="overviewTitle"
class="menutitle">Overview</div>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<div onclick="SwitchMenu('overview')" id="overviewTitle"
class="menutitle">Overview</div>
<div id="overview" class="menuitemgroup">
<div class="menuitem">
@@ -281,23 +292,34 @@
</td>
<td height="100%" width="100%">
<!-- Content -->
- <div class="wiki-content"><h1 id="osgi-subsystems">OSGi
Subsystems</h1>
-<h2 id="introduction">Introduction</h2>
+ <div class="wiki-content"><style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="osgi-subsystems">OSGi Subsystems<a class="headerlink"
href="#osgi-subsystems" title="Permanent link">¶</a></h1>
+<h2 id="introduction">Introduction<a class="headerlink" href="#introduction"
title="Permanent link">¶</a></h2>
<p>Apache Aries Subsystems is the Reference Implementation of the OSGi
Subsystems Specification, chapter 134 of the
-<a href="http://www.osgi.org/Specifications/HomePage"; title="OSGi Enterprise
specifications">OSGi Enterprise specifications</a>. The Aries 1.x components
implement the 1.0 version of the Subsystem spec. Aries 2.x and newer implement
the 1.1 version of the OSGi Subsystems.</p>
-<h2 id="getting-started">Getting started</h2>
+<a href="http://www.osgi.org/Specifications/HomePage"; title="OSGi Enterprise
specifications">OSGi Enterprise specifications</a>. The Aries 1.x components
implement the 1.0 version of the Subsystem spec. Aries 2.x and newer implement
the 1.1 version of OSGi Subsystems.</p>
+<h2 id="getting-started">Getting started<a class="headerlink"
href="#getting-started" title="Permanent link">¶</a></h2>
<p>This section shows the bundles to install to get the Subsystems
implementation running in your favourite OSGi Framework.</p>
<p>The Aries Subsystem implementation uses the OSGi Coordination service, the
OSGi
Resolver service, the OSGi Repository service and integrates with the OSGi
Configuration Admin service. Additional
dependencies are the Aries Util bundle, the Equinox Region bundle and SLF4J
for logging.</p>
<p>The following are downloadable links (from Maven central) that
provide all the required components to get subsystems up and running with
Apache
-Felix. Note that the Felix distribution comes with OSGi Repository and
Resolver implementations so these
+Felix. Note that the Felix Framework distribution comes with OSGi Repository
and Resolver implementations so these
do not need to be added. (When running Aries Subsystems with another OSGi
Framework these
must be provided.)</p>
<ul>
-<li><a
href="https://repo1.maven.org/maven2/org/apache/aries/subsystem/org.apache.aries.subsystem.api/2.0.1/org.apache.aries.subsystem.api-2.0.1.jar";>org.apache.aries.subsystem.api</a></li>
-<li><a
href="https://repo1.maven.org/maven2/org/apache/aries/subsystem/org.apache.aries.subsystem.core/2.0.1/org.apache.aries.subsystem.core-2.0.1.jar";>org.apache.aries.subsystem.core</a></li>
+<li><a
href="https://repo1.maven.org/maven2/org/apache/aries/subsystem/org.apache.aries.subsystem.api/2.0.2/org.apache.aries.subsystem.api-2.0.2.jar";>org.apache.aries.subsystem.api</a></li>
+<li><a
href="https://repo1.maven.org/maven2/org/apache/aries/subsystem/org.apache.aries.subsystem.core/2.0.2/org.apache.aries.subsystem.core-2.0.2.jar";>org.apache.aries.subsystem.core</a></li>
<li><a
href="http://repo1.maven.org/maven2/org/apache/aries/org.apache.aries.util/1.1.0/org.apache.aries.util-1.1.0.jar";>org.apache.aries.util</a></li>
<li><a
href="https://repo1.maven.org/maven2/org/apache/felix/org.apache.felix.configadmin/1.8.6/org.apache.felix.configadmin-1.8.6.jar";>org.apache.felix.configadmin</a></li>
<li><a
href="http://repo1.maven.org/maven2/org/apache/felix/org.apache.felix.coordinator/1.0.0/org.apache.felix.coordinator-1.0.0.jar";>org.apache.felix.coordinator</a></li>
@@ -348,14 +370,14 @@ by looking at the services registered by
<p>Each installed subsystem is represented by a serparate service.</p>
-<h2 id="tools">Tools</h2>
+<h2 id="tools">Tools<a class="headerlink" href="#tools" title="Permanent
link">¶</a></h2>
<p>The Apache Aries community provides a number of tools that facilitate
working with OSGi Subsystems:</p>
<ul>
<li>Subsystem Gogo Command - a Gogo command to work with subsystems, for more
info see below.</li>
<li><a href="http://aries.apache.org/modules/esaanttask.html";>esa-ant-task</a>
- an Ant task to create .esa archives.</li>
<li><a
href="http://aries.apache.org/modules/esamavenpluginproject.html";>eas-maven-plugin</a>
- a Maven plugin to create .esa archives.</li>
</ul>
-<h3 id="subsystem-gogo-command">Subsystem Gogo Command</h3>
+<h3 id="subsystem-gogo-command">Subsystem Gogo Command<a class="headerlink"
href="#subsystem-gogo-command" title="Permanent link">¶</a></h3>
<p><a
href="https://svn.apache.org/repos/asf/aries/trunk/subsystem/subsystem-gogo-command";>https://svn.apache.org/repos/asf/aries/trunk/subsystem/subsystem-gogo-command</a>
contains a simple bundle with Gogo commands
to control subsystems.</p>
<p>After installing the gogo command bundle you can execute subsystem
commands, for example:</p>
@@ -405,7 +427,7 @@ following single command, starts 3 bundl
</pre></div>
-<h3 id="subsystem-gogo-commands">Subsystem gogo commands</h3>
+<h3 id="subsystem-gogo-commands">Subsystem gogo commands<a class="headerlink"
href="#subsystem-gogo-commands" title="Permanent link">¶</a></h3>
<p>The following commands are available from the subsystem-gogo-command
bundle:</p>
<ul>
<li><code>subsystem:install <url></code> - Install and resolve a
subsystem.</li>
@@ -416,7 +438,7 @@ following single command, starts 3 bundl
</ul>
<p>Note that, following the OSGi Subsystem specification, dependent subsystems
are only stopped and uninstalled when the last using subsystem
is stopped/uninstalled.</p>
-<h2 id="development">Development</h2>
+<h2 id="development">Development<a class="headerlink" href="#development"
title="Permanent link">¶</a></h2>
<p>The Aries Subsystems code base can be found at the following location: <a
href="https://svn.apache.org/repos/asf/aries/trunk/subsystem";>https://svn.apache.org/repos/asf/aries/trunk/subsystem</a></p></div>
<!-- Content -->
</td>
