Author: buildbot
Date: Tue Feb 2 19:47:42 2016
New Revision: 979309
Log:
Staging update by buildbot for sling
Modified:
websites/staging/sling/trunk/content/ (props changed)
websites/staging/sling/trunk/content/documentation/development/slingstart.html
Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Feb 2 19:47:42 2016
@@ -1 +1 @@
-1728171
+1728194
Modified:
websites/staging/sling/trunk/content/documentation/development/slingstart.html
==============================================================================
---
websites/staging/sling/trunk/content/documentation/development/slingstart.html
(original)
+++
websites/staging/sling/trunk/content/documentation/development/slingstart.html
Tue Feb 2 19:47:42 2016
@@ -165,8 +165,23 @@ Each run mode is associated with a set o
<p>Special configurations can be marked with a leading ":" of the pid. Special
configurations are not added to the OSGi config admin. There are some
predefined special configurations</p>
<ul>
<li>:web.xml This configuration must be part of the :webapp runmode and
contains a complete web.xml for the web application</li>
-<li>:bootstrap This configuration must be part of either the :boot, :base,
:standalone, or :webapp run mode and define the contents for bootstrap command
file executed by Launchpad.</li>
+<li>:bootstrap This configuration must be part of either the :boot, :base,
:standalone, or :webapp run mode and define the contents for the bootstrap
command file executed by Launchpad. </li>
</ul>
+<h4 id="bootstrap-command-file">Bootstrap Command File<a class="headerlink"
href="#bootstrap-command-file" title="Permanent link">¶</a></h4>
+<p>The bootstrap configuration is a text block consisting of uninstall
directives. This block is only executed on the first startup.</p>
+<div class="codehilite"><pre><span class="k">[feature name=:launchpad]</span>
+
+<span class="k">[configurations]</span>
+ <span class="c"># uninstall obsolete bundles which are neither not required
anymore or are</span>
+ <span class="c"># replaced with new bundles</span>
+<span class="err">:bootstrap</span>
+ <span class="err">uninstall</span> <span
class="err">org.apache.sling.fragment.activation</span> <span
class="err">1.2</span>
+ <span class="err">uninstall</span> <span
class="err">org.apache.sling.installer.api</span> <span
class="err">[1.0,2.0)</span>
+ <span class="err">uninstall</span> <span
class="err">org.apache.sling.tests</span>
+</pre></div>
+
+
+<p>Each uninstall directive starts with the text "uninstall" followed by the
bundle symbolic name. A version range can be specified as well. If no version
information is specified, the bundle with that symbolic name is uninstalled on
startup. If a version is specified, the bundle is only uninstalled if it's
installed with the exact same version. If a range is specified, the bundle is
only uninstalled, if the version is within that range.</p>
<h3 id="settings">Settings<a class="headerlink" href="#settings"
title="Permanent link">¶</a></h3>
<p>Settings are key value pairs that are added to the framework properties.
For now, only settings for the run modes :boot, :base, :standalone, or :webapp
are supported.</p>
<h3 id="features">Features<a class="headerlink" href="#features"
title="Permanent link">¶</a></h3>
@@ -362,7 +377,7 @@ Each run mode is associated with a set o
<span class="nt"></plugin></span>
</pre></div>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1717776 by cziegeler on Thu, 3 Dec 2015 14:42:23 +0000
+ Rev. 1728194 by cziegeler on Tue, 2 Feb 2016 19:47:33 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
