svn commit: r977312 - in /websites/staging/sling/trunk/content: ./ documentation/bundles/file-installer-provider.html

[bu...@apache.org]

Author: buildbot
Date: Fri Jan  8 16:48:55 2016
New Revision: 977312

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:48:55 2016
@@ -1 +1 @@
-1723757
+1723758

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:48:55 2016
@@ -150,7 +150,7 @@ Of course, these are the simple rules. T
 <h2 id="configurations">Configurations<a class="headerlink" href="#configurations" title="Permanent link">&para;</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">&para;</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>
+<p>Custom artifacts are handled by the OSGi installer depending on the installed plugins. Have a look at the OSGi installer and its plugins for more information.</p>
 <h2 id="runmode-support">Runmode Support<a class="headerlink" href="#runmode-support" title="Permanent link">&para;</a></h2>
 <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>&lt;sling.fileinstall.dir&gt;/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>
@@ -159,7 +159,7 @@ Of course, these are the simple rules. T
 <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. 1723757 by kwin on Fri, 8 Jan 2016 16:47:45 +0000
+        Rev. 1723758 by kwin on Fri, 8 Jan 2016 16:48:46 +0000
       </div>
       <div class="trademarkFooter"> 
         Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project