Closed kwin closed 3 months ago
Another bunch of issues have been raised recently:
Although those issue wouldn't be prevented by such a feature, verifying the fix locally would be a lot easier with an analyser for that.
I opened https://issues.apache.org/jira/browse/SLING-12026 for the implementation of the according Feature Model Analyser.
Closed #2587 after updating WCM 2.32.2 -> 2.23.4
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.
The Sonar rule described in https://experienceleague.adobe.com/docs/experience-manager-cloud-manager/using/how-to-use/custom-code-quality-rules.html?lang=en#product-apis-annotated-with-providertype-should-not-be-implemented-or-extended-by-customers is currently only executed in Cloud Manager. It would be helpful to check the code for implementation of interfaces marked as "providertype" even locally.
Recently the check has been raised to Critical severity which triggers issues e.g. in