Author: buildbot
Date: Fri Jan 8 16:47:54 2016
New Revision: 977311
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:47:54 2016
@@ -1 +1 @@
-1723756
+1723757
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:47:54 2016
@@ -152,14 +152,14 @@ Of course, these are the simple rules. T
<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 (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>The file installer supports run modes for installing artifacts (added with
<a href="https://issues.apache.org/jira/browse/SLING-4478";>SLING-4478</a>).
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. 1723756 by kwin on Fri, 8 Jan 2016 16:45:58 +0000
+ Rev. 1723757 by kwin on Fri, 8 Jan 2016 16:47:45 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
