You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by bd...@apache.org on 2018/11/20 14:39:22 UTC
[sling-org-apache-sling-capabilities] branch master updated:
SLING-8120 - update README for the modified behaviors
This is an automated email from the ASF dual-hosted git repository.
bdelacretaz pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-org-apache-sling-capabilities.git
The following commit(s) were added to refs/heads/master by this push:
new 1f7012e SLING-8120 - update README for the modified behaviors
1f7012e is described below
commit 1f7012e03db0de14eabfa7953c81b63ec4776747
Author: Bertrand Delacretaz <bd...@apache.org>
AuthorDate: Tue Nov 20 15:39:10 2018 +0100
SLING-8120 - update README for the modified behaviors
---
README.md | 4 ----
1 file changed, 4 deletions(-)
diff --git a/README.md b/README.md
index b6bd142..0727fe8 100644
--- a/README.md
+++ b/README.md
@@ -11,10 +11,6 @@ The servlet provided by this module allows for creating Capabilities HTTP endpoi
on a Sling instance: Resources that provide information on which services are available,
version levels etc.
-To avoid exposing more information than strictly needed, this module provides two mechanisms,
-described below, to control where resources that expose capabilities can be found in the Sling
-resource tree, as well as which `CapabilitiesSource` services are considered by those resources.
-
The example configuration below shows the JSON vocabulary used to expose capabilities.
For now, we have one module which provides a `CapabilitiesSource`, that's the [sling-org-apache-sling-capabilities-jcr](https://github.com/apache/sling-org-apache-sling-capabilities-jcr) module which provides information on the JCR repository.