[sling-org-apache-sling-feature-analyser] branch master updated: Updated readme.md

[da...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

davidb pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-org-apache-sling-feature-analyser.git


The following commit(s) were added to refs/heads/master by this push:
     new 2df59ea  Updated readme.md
2df59ea is described below

commit 2df59eaa9bcd7a5fdee51900711f56543a3714ad
Author: David Bosschaert <bo...@adobe.com>
AuthorDate: Fri Feb 21 13:32:42 2020 +0000

    Updated readme.md
---
 readme.md | 21 +--------------------
 1 file changed, 1 insertion(+), 20 deletions(-)

diff --git a/readme.md b/readme.md
index 8d2309f..1be6ebc 100644
--- a/readme.md
+++ b/readme.md
@@ -30,25 +30,6 @@ information as part of the check, to ensure that bundles don't import packages o
 
 * `apis-jar`: validates that the `sourceId` property of a bundle, if defined, is a comma-separated value list of artifact ids.
 
-There are a number of analysers which relate to API Region definitions in Feature Models. 
-
-* `api-regions`: This analyser ensures that packages listed as exports in API-Regions sections are actually exported by a bundle that's part of the feature.
-
-* `api-regions-dependencies`: This analyser checks that packages in API regions listed earlier in the API-Regions declaration have no dependency on API regions listed later in the list. This include `Import-Package` style dependencies and also uses-clause type dependencies. Later API regions also include packages from earlier declared API regions, but not the other way around.
-  * Configuration parameters:
-  * `exporting-apis`: the name of the region that provides the visible APIs.
-  * `hiding-apis`: the name of the region that is 'hidden' i.e. not as visible as the exporting one. The
-packages in the `exporting-api` cannot depend on any packages from this region. 
-
-* `api-regions-duplicates`: This analyser ensures that packages are only listed in one region
-in a given feature. If the same package is listed in multiple regions this will be an error.
-
-* `api-regions-check-order`: This analyser checks that regions are defined in the specified 
-order and that the same region is only declared once. Later regions inherit the packages
-expose in earlier regions in the list, so the order is important.
-  * Configuration parameters:
-  * `order`: A comma separated list of the region names declaring the order in which they should be found. Not all regions declared must be present, but if they are present this
-order must be obeyed.
- 
+Additional analysers in relation to Feature Model API Regions can be found here: https://github.com/apache/sling-org-apache-sling-feature-extension-apiregions
 
 For further documentation see: https://github.com/apache/sling-org-apache-sling-feature/blob/master/readme.md