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 2abb0b1 Automatic website deployment
2abb0b1 is described below
commit 2abb0b1af984dbac20cfd4d86b0ddec7a97278a3
Author: jenkins <[email protected]>
AuthorDate: Wed Mar 27 15:37:53 2019 +0000
Automatic website deployment
---
documentation/bundles/jcr-installer-provider.html | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/documentation/bundles/jcr-installer-provider.html
b/documentation/bundles/jcr-installer-provider.html
index c1e03c7..43e0e14 100644
--- a/documentation/bundles/jcr-installer-provider.html
+++ b/documentation/bundles/jcr-installer-provider.html
@@ -81,7 +81,7 @@
<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" name="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 comma. For
example, if started with run modes <code>dev</code>, <code>a1</code>, and
<code>public</code>, folders like <code>install.dev</c [...]
+<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 [...]
<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" name="start-level-support">Start Level
Support</a></h3>
<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>
@@ -169,7 +169,7 @@ curl -X MKCOL
http://admin:admin@localhost:8080/apps/jcrtest/install
</ul></section></div></div>
<footer class="footer">
<div class="revisionInfo">
- Last modified by <span class="author">Konrad
Windszus</span> on <span class="comment">Thu Mar 14 15:43:58 2019 +0100</span>
+ Last modified by <span class="author">Konrad
Windszus</span> on <span class="comment">Wed Mar 27 16:27:03 2019 +0100</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>
