Author: buildbot
Date: Fri Oct 7 08:04:25 2016
New Revision: 998995
Log:
Staging update by buildbot for sling
Modified:
websites/staging/sling/trunk/content/ (props changed)
websites/staging/sling/trunk/content/documentation/bundles/jcr-installer-provider.html
Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Oct 7 08:04:25 2016
@@ -1 +1 @@
-1763692
+1763693
Modified:
websites/staging/sling/trunk/content/documentation/bundles/jcr-installer-provider.html
==============================================================================
---
websites/staging/sling/trunk/content/documentation/bundles/jcr-installer-provider.html
(original)
+++
websites/staging/sling/trunk/content/documentation/bundles/jcr-installer-provider.html
Fri Oct 7 08:04:25 2016
@@ -117,7 +117,7 @@ h2:hover > .headerlink, h3:hover > .head
<p>The JCR installer provider scans the JCR repository for artifacts and
provides them to the <a href="/documentation/bundles/osgi-installer.html">OSGI
installer</a>.</p>
<h2 id="configuration-and-scanning">Configuration and Scanning<a
class="headerlink" href="#configuration-and-scanning" title="Permanent
link">¶</a></h2>
<p>The JCR installer provider can be configured with weighted paths which are
scanned. By default, the installer scans in <em>/apps</em> and <em>/libs</em>
where artifacts found in <em>/apps</em> get a higher priority. The installer
does a deep scan and uses a regular expression to detect folders containing
artifacts to be installed. By default, artifacts from within a folder named
<em>install</em> are provided to the OSGi installer.</p>
-<p>If such an install folder contains a binary artifact (e.g. a bundle or a
config file as described in <a
href="/documentation/bundles/configuration-installer-factory.html">Configuration
Installer Factory</a> this is provided to the OSGi installer. </p>
+<p>If such an install folder contains a binary artifact (e.g. a bundle or a
config file as described in <a
href="/documentation/bundles/configuration-installer-factory.html">Configuration
Installer Factory</a>) this is provided to the OSGi installer. </p>
<p>In addition every node of type <em>sling:OsgiConfig</em> is provided as a
configuration to the installer. This has the advantage of leveraging the JCR
structure better than binary files, but has the known limitations outlined in
<a href="https://issues.apache.org/jira/browse/SLING-4183";>SLING-4183</a> and
<a href="https://issues.apache.org/jira/browse/SLING-2477";>SLING-2477</a>,
therefore it is recommended to stick to one of the binary formats described in
<a
href="/documentation/bundles/configuration-installer-factory.html">Configuration
Installer Factory</a>.</p>
<p>The JCR installer provider does not check or scan the artifacts itself, the
detection and installation is deferred to the OSGi installer.</p>
<h3 id="runmode-support">Runmode Support<a class="headerlink"
href="#runmode-support" title="Permanent link">¶</a></h3>
@@ -233,7 +233,7 @@ As JCR properties do not support all Jav
<li>JCR installer provider (<a
href="http://svn.apache.org/repos/asf/sling/trunk/installer/providers/jcr";>org.apache.sling.installer.provider.jcr</a>)</li>
</ul>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1763692 by kwin on Fri, 7 Oct 2016 08:03:12 +0000
+ Rev. 1763693 by kwin on Fri, 7 Oct 2016 08:04:16 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
