Open adellanegra opened 1 year ago
@adellanegra you can ignore those warnings. We currently dont have plans moving them over to Editable Templates as that would only add to the complexity of those features with no benefit (other than eliminating those warnings).
Required Information
Expected Behavior
no issues in the build project report
Actual Behavior
I am working on AEM as a Cloud Service and following the documentation https://adobe-consulting-services.github.io/acs-aem-commons/pages/maven.html I have included in the pom files the dependencies for installing the acs commons automatically in the build process.
The deployment via cloud service finishes correctly but the code quality step reports almost 42 minor issues related to the templates and the components included in the packages. Below the issues:
The current acs commons version is still using static templates and legacy components; are you planning to covert them to compatible and new version or shoud I ignore those warnings?
Steps to Reproduce
https://adobe-consulting-services.github.io/acs-aem-commons/pages/maven.html and trigger the deployment via cloud manager