This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/sling-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 4b72108 Automatic website deployment from
https://builds.apache.org/job/Sling/job/sling-site/job/master/371/
4b72108 is described below
commit 4b721084ca59e760a91d3593d8c6406b8a9221af
Author: jenkins <[email protected]>
AuthorDate: Thu Jun 4 15:49:16 2020 +0000
Automatic website deployment from
https://builds.apache.org/job/Sling/job/sling-site/job/master/371/
---
documentation/bundles/jcr-installer-provider.html | 12 +++++++-----
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git a/documentation/bundles/jcr-installer-provider.html
b/documentation/bundles/jcr-installer-provider.html
index 818e3d3..c1e04cb 100644
--- a/documentation/bundles/jcr-installer-provider.html
+++ b/documentation/bundles/jcr-installer-provider.html
@@ -120,14 +120,16 @@
<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 <code>sling:OsgiConfig</code> 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/ [...]
<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><a href="#runmode-support" id="runmode-support">Runmode Support</a></h3>
-<p>The JCR installer supports run modes for installing artifacts. By default
folders named <code>install</code> are checked for artifacts. If Apache Sling
is started with one (or more run modes), all folders named
<code>install.[RUNMODE]</code> are scanned as well. To be precise, the folder
name can be followed by any number of run modes separated by dot
(<code>.</code>). For example, if started with run modes <code>dev</code>,
<code>a1</code>, and <code>public</code>, folders like <code [...]
+<h2><a href="#run-mode-support" id="run-mode-support">Run Mode Support</a></h2>
+<p>The JCR installer supports <a
href="sling-settings-org-apache-sling-settings.html">run modes</a> for
installing artifacts. By default folders named <code>install</code> are checked
for artifacts. If Apache Sling is started with one (or more run modes), all
folders named <code>install.[RUNMODE]</code> are scanned as well. To be
precise, the folder name can be followed by any number of run modes separated
by dot (<code>.</code>). For example, if started with run modes
<code>dev</code>, [...]
<p>Artifacts from folders with a run mode get a higher priority. For example
by default, an <code>install</code> folder underneath <code>/libs</code> gets
the priority <code>50</code>. For each run mode in the folder name, this
priority is increased by <code>1</code>, so <code>install.dev</code> has
<code>51</code> and <code>install.a1.dev</code> has <code>52</code>.</p>
-<h3><a href="#start-level-support" id="start-level-support">Start Level
Support</a></h3>
+<h2><a href="#start-level-support" id="start-level-support">Start Level
Support</a></h2>
<p>If the parent folder of a bundle has a name which is a number, this is used
as the start level (when installing the bundle for the first time, compare with
<a href="https://issues.apache.org/jira/browse/SLING-2011";>SLING-2011</a>). So
e.g. a bundle in the path <code>/libs/sling/install/15/somebundle.jar</code> is
having the start level <code>15</code>.</p>
-<h1><a href="#write-back-support" id="write-back-support">Write Back
Support</a></h1>
+<h2><a href="#write-back-support" id="write-back-support">Write Back
Support</a></h2>
<p>The JCR installer supports writing back of configurations which are changed
by some other ways, e.g by using the Apache Felix web console. If this is a new
configuration which was not originally stored in the repository, a new
configuration is stored under <code>/apps/sling/install</code>. The highest
search path is used together with a configurable folder
(<code>sling/install</code> in this case). If a configuration is changed which
already exists in the repository, then it depends w [...]
<p>Write back can be turned off by configuration.</p>
+<h2><a href="#pausing-the-provider" id="pausing-the-provider">Pausing the
provider</a></h2>
+<p>In version 3.1.8 (<a
href="https://issues.apache.org/jira/browse/SLING-3747";>SLING-3747</a>) a
mechanism has been added which pauses the scanning of artifacts. Whenever there
is at least one child node below
<code>/system/sling/installer/jcr/pauseInstallation</code> (path configurable),
the provider will be paused i.e. not provide any artifacts to the OSGi
installer. This is reasonable to do while executing operations which rely on
certain services not being restarted. Every deploymen [...]
<h1><a href="#example" id="example">Example</a></h1>
<p>Here's a quick walkthrough of the JCR installer functionality.</p>
<h2><a href="#installation" id="installation">Installation</a></h2>
@@ -214,7 +216,7 @@ curl -X MKCOL
http://admin:admin@localhost:8080/apps/jcrtest/install
</div><footer class="footer">
<div class="content has-text-centered is-small">
<div class="revisionInfo">
- Last modified by <span class="author">Konrad
Windszus</span> on <span class="comment">Wed Mar 27 16:27:03 2019 +0100</span>
+ Last modified by <span class="author">Konrad
Windszus</span> on <span class="comment">Thu Jun 4 17:45:40 2020 +0200</span>
</div> <p>
Apache Sling, Sling, Apache, the Apache feather logo,
and the Apache Sling project logo are trademarks of The Apache Software
Foundation. All other marks mentioned may be trademarks or registered
trademarks of their respective owners.
</p><p>
