Konrad Windszus

Probably `subschemaSubentry` can be used to retrieve the hierarchy: https://tools.ietf.org/html/rfc4512#section-4.2

This seems to duplicate #338.

I also opened https://issues.apache.org/jira/browse/SLING-10878 for Sling Testing Client.

This is related to https://github.com/adobe/aem-site-template-standard/issues/92

Another bunch of issues have been raised recently: 1. https://github.com/Netcentric/accesscontroltool/issues/671 2. https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues/3185 3. https://github.com/ist-dresden/composum-nodes/issues/310 4. https://github.com/adobe/aem-core-wcm-components/issues/2587 Although those issue wouldn't be prevented by such a feature, verifying the fix locally...

I opened https://issues.apache.org/jira/browse/SLING-12026 for the implementation of the according Feature Model Analyser.

This is supported with the bnd plugin provided at https://github.com/apache/sling-org-apache-sling-providertype-bnd-plugin. Outside the scope of the aemanalyser.

Somehow the capabilities being calculated in https://github.com/apache/sling-org-apache-sling-feature-analyser/blob/master/src/main/java/org/apache/sling/feature/analyser/task/impl/CheckRequirementsCapabilities.java#L65 take the current java version as basis. Somehow one needs to override that.

Probably one can use the parameter https://github.com/apache/sling-slingfeature-maven-plugin/blob/d8a0bffbe4d1715c9d0f8791bb4db74772d7e9ad/src/main/java/org/apache/sling/feature/maven/mojos/AnalyseFeaturesMojo.java#L73 to set the right execution environment. Not sure which artifact to reference here, though.

I finally found the culprit and reported https://issues.apache.org/jira/browse/SLING-10288 for that.