This is an automated email from the ASF dual-hosted git repository.
kwin pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-site.git
The following commit(s) were added to refs/heads/master by this push:
new cb2ac48 Improve SLING-5888 documentation
new b0fae09 Merge pull request #46 from wimsymons/patch-1
cb2ac48 is described below
commit cb2ac48f294ca0f530a4dc531d349402e8e055d8
Author: Wim Symons <[email protected]>
AuthorDate: Fri May 15 10:56:40 2020 +0200
Improve SLING-5888 documentation
It wasn't immediately clear to me that there are 2 cases the health check
will fail on.
It seemed the text was chopped off after "The health check will fail in the
following cases:".
This edit should improve that.
---
src/main/jbake/content/documentation/bundles/osgi-installer.md | 3 +++
1 file changed, 3 insertions(+)
diff --git a/src/main/jbake/content/documentation/bundles/osgi-installer.md
b/src/main/jbake/content/documentation/bundles/osgi-installer.md
index 878c2ef..d807714 100644
--- a/src/main/jbake/content/documentation/bundles/osgi-installer.md
+++ b/src/main/jbake/content/documentation/bundles/osgi-installer.md
@@ -106,7 +106,10 @@ A provider provides artifacts, e.g. by scanning a
directory or a database etc.
The OSGi installer provides a [Sling Health
Check](/documentation/bundles/sling-health-check-tool.html) which validates
that the processed OSGi installer resources have the correct state
([SLING-5888](https://issues.apache.org/jira/browse/SLING-5888)).
By default it will only check resources with a URL prefix `jcrinstall:/apps/`,
so only the resources being provided through the [JCR Installer
Provider](/documentation/bundles/jcr-installer-provider.html) initially located
below the repository resource `/apps/` are considered.
+
The health check will fail in the following cases:
+* Bundles Installation Failure
+* Configuration Installation Failure
### Bundles Installation Failure
