incubator-sling-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r881581 - in /websites/staging/sling/trunk/content: ./ old-stuff/assembly.html
Date Mon, 07 Oct 2013 17:00:16 GMT
Author: buildbot
Date: Mon Oct  7 17:00:15 2013
New Revision: 881581

Log:
Staging update by buildbot for sling

Modified:
    websites/staging/sling/trunk/content/   (props changed)
    websites/staging/sling/trunk/content/old-stuff/assembly.html

Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Oct  7 17:00:15 2013
@@ -1 +1 @@
-1529997
+1529998

Modified: websites/staging/sling/trunk/content/old-stuff/assembly.html
==============================================================================
--- websites/staging/sling/trunk/content/old-stuff/assembly.html (original)
+++ websites/staging/sling/trunk/content/old-stuff/assembly.html Mon Oct  7 17:00:15 2013
@@ -134,7 +134,7 @@
 
 <p>To control the selection and installation of bundles, the following parameters may
be used:</p>
 <ul>
-<li><strong>version</strong> - The version of the bundle to install. This
is a version range specification as per chapter 3.2.5 Version Ranges of the OSGi core specification.
When this parameter is declared as a single version - eg. <em>1.2.3</em> - it
is interpreted as the version range <em>~[1.2.3, &infin;~)</em>. The default
value is <em>~[0.0.0,&infin;~)</em> to install the most recent version of
the bundle available.</li>
+<li><strong>version</strong> - The version of the bundle to install. This
is a version range specification as per chapter 3.2.5 Version Ranges of the OSGi core specification.
When this parameter is declared as a single version - eg. <em>1.2.3</em> - it
is interpreted as the version range <em>[1.2.3,&infin;)</em>. The default
value is <em>[0.0.0,&infin;)</em> to install the most recent version of the
bundle available.</li>
 <li><strong>startlevel</strong> - The start level to set for the bundle.
This may be any positive integer value. Default value is undefined to use the current initial
bundle start level of the framework.</li>
 <li><strong>entry</strong> - The path of the Assembly Bundle entry providing
the data to be installed.</li>
 <li><strong>linked</strong> - Defines whether the bundle should be started
and stopped together with the Assembly to which the bundle belongs. Default value is <code>true</code>.</li>
@@ -165,7 +165,7 @@
 <h3 id="nomen-est-omen">Nomen est Omen</h3>
 <p>The symbolic name of a bundle should reflect its contents. A bundle should generally
only contain a single subtree in the virtual package tree. The symbolic name of the bundle
should be the root package contained within. For example, consider a bundle containing the
packages <code>org.apache.sling.sample</code>, <code>org.apache.sling.sample.impl</code>,
<code>org.apache.sling.more</code>. The bundle would the be named <code>org.apache.sling.sample</code>.</p>
       <div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
-        Rev. 1529997 by dklco on Mon, 7 Oct 2013 16:57:51 +0000
+        Rev. 1529998 by dklco on Mon, 7 Oct 2013 17:00:03 +0000
       </div>
       <div class="trademarkFooter"> 
         Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project



Mime
View raw message