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 908eac2 Automatic website deployment from
https://ci-builds.apache.org/job/Sling/job/modules/job/sling-site/job/master/64/
908eac2 is described below
commit 908eac20af76cd83ed715cb729e7759c26a3428e
Author: jenkins <[email protected]>
AuthorDate: Tue Oct 27 22:37:45 2020 +0000
Automatic website deployment from
https://ci-builds.apache.org/job/Sling/job/modules/job/sling-site/job/master/64/
---
documentation/bundles/sling-health-checks.html | 10 +++++-----
documentation/development/release-management.html | 6 +++---
2 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/documentation/bundles/sling-health-checks.html
b/documentation/bundles/sling-health-checks.html
index 9cf96ae..7ab976b 100644
--- a/documentation/bundles/sling-health-checks.html
+++ b/documentation/bundles/sling-health-checks.html
@@ -122,15 +122,15 @@
<h1><a href="#best-location-for-health-checks"
id="best-location-for-health-checks">Best location for Health Checks</a></h1>
<p>It is best practice to place health check next to the functionality they
check. Also documentation of those check should be provided along with the
documentation of the functionality.</p>
<p>The below checks are exceptions to that rule as they are generic in what
they check (but still require Sling features, that's whey they are not in
Apache Felix).</p>
-<h1><a href="#apache-sling-health-check-support-module"
id="apache-sling-health-check-support-module">Apache Sling Health Check Support
Module</a></h1>
+<h1><a href="#apache-sling-health-check-support-bundle"
id="apache-sling-health-check-support-bundle">Apache Sling Health Check Support
Bundle</a></h1>
<table>
<thead>
<tr><th>Check </th><th> PID </th><th> Factory </th><th> Description</th></tr>
</thead>
<tbody>
-<tr><td>Default Logins Check </td><td>
org.apache.sling.hc.support.DefaultLoginsHealthCheck </td><td> yes </td><td>
Set a list of default logins in config array <code>logins</code> separed by
<code>:</code>, e.g. <code>author:author</code></td></tr>
-<tr><td>Scripted Check </td><td>
org.apache.felix.hc.generalchecks.ScriptedHealthCheck </td><td> yes </td><td>
Allows to run an arbitrary script in the same way as the Scripted Check from
from Apache Felix bundle <a
href="https://github.com/apache/felix/blob/trunk/healthcheck/README.md#general-purpose-health-checks-available-out-of-the-box";>general
checks</a>, except that this check allows to use files being loaded from JCR
by using a <code>scriptUrl</code> with prefix <code>jcr:</code>, [...]
-<tr><td>Request Status Health Check </td><td> <em>Deprecated</em> </td><td>
</td><td> Use instead the corresponding check from <a
href="https://github.com/apache/felix/blob/trunk/healthcheck/README.md#general-purpose-health-checks-available-out-of-the-box";>general
checks</a></td></tr>
+<tr><td>Default Logins Check </td><td>
org.apache.sling.hc.support.DefaultLoginsHealthCheck </td><td> yes </td><td>
Set a list of default logins in config array <code>logins</code> separated by
<code>:</code>, e.g. <code>author:author</code></td></tr>
+<tr><td>Scripted Check </td><td>
org.apache.sling.hc.support.impl.ScriptedHealthCheck </td><td> yes </td><td>
Allows to run an arbitrary script in the same way as the Scripted Check
<code>org.apache.felix.hc.generalchecks.ScriptedHealthCheck</code> from Apache
Felix bundle <a
href="https://github.com/apache/felix-dev/blob/master/healthcheck/README.md#general-purpose-health-checks-available-out-of-the-box";>general
checks</a>, except that this check allows to use files being loaded from JC
[...]
+<tr><td>Request Status Health Check </td><td> <em>Deprecated</em> </td><td>
</td><td> Use instead the corresponding check from <a
href="https://github.com/apache/felix-dev/blob/master/healthcheck/README.md#general-purpose-health-checks-available-out-of-the-box";>general
checks</a></td></tr>
</tbody>
</table>
<h1><a href="#health-checks-as-server-side-junit-tests"
id="health-checks-as-server-side-junit-tests">Health Checks as server-side
JUnit tests</a></h1>
@@ -146,7 +146,7 @@ remote testing utilities, and also as plain Health Checks
for monitoring or trou
</div><footer class="footer">
<div class="content has-text-centered is-small">
<div class="revisionInfo">
- Last modified by <span
class="author">georg.henzler</span> on <span class="comment">Wed Apr 3 20:32:51
2019 +0200</span>
+ Last modified by <span
class="author">georg.henzler</span> on <span class="comment">Tue Oct 27
23:34:03 2020 +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>
diff --git a/documentation/development/release-management.html
b/documentation/development/release-management.html
index 157ab52..cbef293 100644
--- a/documentation/development/release-management.html
+++ b/documentation/development/release-management.html
@@ -519,14 +519,14 @@ ssb 2048R/226BCE00 2016-01-21
</ol>
</li>
<li>
-<p>Now send an email to [email protected] requesting a PMC member to add
your public key to <a
href="https://downloads.apache.org/sling/KEYS";>https://downloads.apache.org/sling/KEYS</a>
by adding it via SVN to <a
href="https://dist.apache.org/repos/dist/release/sling/KEYS";>https://dist.apache.org/repos/dist/release/sling/KEYS</a>,
e.g. via</p>
+<p>Now add your public key to <a
href="https://downloads.apache.org/sling/KEYS";>https://downloads.apache.org/sling/KEYS</a>
by adding it via SVN to <a
href="https://dist.apache.org/repos/dist/release/sling/KEYS";>https://dist.apache.org/repos/dist/release/sling/KEYS</a>.
This is only possible for PMC members (for a reasoning look at <a
href="http://www.apache.org/dev/release.html#upload-ci";>http://www.apache.org/dev/release.html#upload-ci</a>).
If you are not a PMC member, please ask one [...]
<pre><code>$ svn checkout https://dist.apache.org/repos/dist/release/sling/
sling --depth empty
$ cd sling
$ svn up KEYS
</code></pre>
</li>
</ol>
-<p>Then edit the <code>KEYS</code> file with your favourite editor and
afterwards</p>
+<p>Add the public key to <code>KEYS</code> file with your favourite editor and
afterwards</p>
<pre><code> $ svn commit -m "my key added" KEYS
</code></pre>
<h2><a href="#appendix-b-deploy-maven-plugin-documentation-if-applicable"
id="appendix-b-deploy-maven-plugin-documentation-if-applicable">Appendix B:
Deploy Maven plugin documentation (if applicable)</a></h2>
@@ -577,7 +577,7 @@ $ svn up KEYS
</div><footer class="footer">
<div class="content has-text-centered is-small">
<div class="revisionInfo">
- Last modified by <span class="author">Cris
Rockwell</span> on <span class="comment">Mon Oct 19 14:29:19 2020 -0400</span>
+ Last modified by <span class="author">Konrad
Windszus</span> on <span class="comment">Tue Oct 27 16:07:42 2020 +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>
