Author: buildbot
Date: Fri Jan 8 16:46:14 2016
New Revision: 977310
Log:
Staging update by buildbot for sling
Modified:
websites/staging/sling/trunk/content/ (props changed)
websites/staging/sling/trunk/content/documentation/bundles/file-installer-provider.html
Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Jan 8 16:46:14 2016
@@ -1 +1 @@
-1723667
+1723756
Modified:
websites/staging/sling/trunk/content/documentation/bundles/file-installer-provider.html
==============================================================================
---
websites/staging/sling/trunk/content/documentation/bundles/file-installer-provider.html
(original)
+++
websites/staging/sling/trunk/content/documentation/bundles/file-installer-provider.html
Fri Jan 8 16:46:14 2016
@@ -129,7 +129,7 @@ h2:hover > .headerlink, h3:hover > .head
<tr>
<td><code>sling.fileinstall.dir</code></td>
<td></td>
-<td>The name/path of the directories to watch. Several directories can be
specified by using a comma separated list.</td>
+<td>The name/path of the directories to watch. Several directories can be
specified by using a comma separated list. Each directory might have
arbitrarily many sub directories (even nested ones) which may contain the
artifacts</td>
</tr>
<tr>
<td><code>sling.fileinstall.interval</code></td>
@@ -146,19 +146,20 @@ h2:hover > .headerlink, h3:hover > .head
<h2 id="bundles">Bundles<a class="headerlink" href="#bundles" title="Permanent
link">¶</a></h2>
<p>Bundles are supported by the OSGi installer. If a bundle jar is added to a
scanned directory, this bundle is installed. If the file is updated/changed,
the bundle is updated. If the file is removed, the bundle gets removed.
Of course, these are the simple rules. The actual action depends by the
overall state of the system and is controlled by the OSGi installer. For
example if already the same bundle with a higher version is installed, when a
bundle is dropped into the install folder, the OSGi installer will perform no
operation.</p>
-<p>Start levels are supported as well by creating a directory with the name of
the start level within the scan directory and putting the bundles within this
directory. For example, if the 'install' folder is scanned, the bundle
'install/3/mybundle.jar' will be installed with start level 3. Without such a
directory the default start level is used.</p>
+<p>Start levels are supported as well by creating a directory with the name of
the start level within the scan directory and putting the bundles within this
directory. For example, if the <code>install</code> folder is scanned, the
bundle <code>install/3/mybundle.jar</code> will be installed with start level
3. Without such a directory the default start level is used.</p>
<h2 id="configurations">Configurations<a class="headerlink"
href="#configurations" title="Permanent link">¶</a></h2>
<p>Configurations are handled by the <a
href="/documentation/bundles/configuration-installer-factory.html">Configuration
Installer Factory</a>. The different formats are described there.</p>
<h2 id="custom-artifacts">Custom Artifacts<a class="headerlink"
href="#custom-artifacts" title="Permanent link">¶</a></h2>
<p>Custom artifacts are handled by the OSGi installer depending on the
installed plugins. Have a look at the OSGi installer and it's plugins for more
information.</p>
<h2 id="runmode-support">Runmode Support<a class="headerlink"
href="#runmode-support" title="Permanent link">¶</a></h2>
-<p>The file installer supports run modes for installing artifacts. Within the
scanned directory, a folder named with the run mode will only provisioning
these artifacts if the respective run mode is active. If an artifact is
associated with several run modes, the name of the directory contains all of
them separated by a dot, for example <em>a1.dev</em>.</p>
+<p>The file installer supports run modes for installing artifacts (added with
(SLING-4478)[https://issues.apache.org/jira/browse/SLING-4478]). Within the
scanned directory, a folder prefixed with "install." and followed by one or
more run modes (separated by ".") will only be considered if all the respective
run modes are active. For example artifacts below a folder named
<code>install.a1.dev</code> are only taken into account if the run modes
<code>a1</code> and <code>dev</code> are both active. </p>
+<p>You can even combine start level and run mode support. Just pay attention
that the run mode foldername must be set on a direct child folder of
<code>sling.fileinstall.dir</code> while the start level must be set directly
on the parent folder of the artifact you want to install. E.g.
<code><sling.fileinstall.dir>/install.a1.dev/3/mybundle.jar</code> will
only be considered if both run modes <code>a1</code> and <code>dev</code> are
set. If this is the case then the according artifact will be installed in start
level 3.</p>
<h1 id="project-info">Project Info<a class="headerlink" href="#project-info"
title="Permanent link">¶</a></h1>
<ul>
<li>File installer provider (<a
href="http://svn.apache.org/repos/asf/sling/trunk/installer/providers/file";>org.apache.sling.installer.provider.file</a>)</li>
</ul>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1648494 by cziegeler on Tue, 30 Dec 2014 09:45:30 +0000
+ Rev. 1723756 by kwin on Fri, 8 Jan 2016 16:45:58 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
