Actually the issue was we were trying to make changes in the existing pom which was created using old archetype. To fix it, we decided to change the whole pom and built the maven project again using recommended maven archetype for AEMaaCS.The analyser should already be included in the new project ar...

Adding more to the Question, the packages throwing errors in the analyser logs are not resolved in AEM cloud local setup as well:So, to use these packages in my code in AEMaaCS, what are the packages I should use?In my local AEM cloud sdk I have already installed forms addon latest tool from Softwar...

Hi Jörg, Thanks for the reply, I tried adding above dependencies just now and also tried embedding the packages in my project similar to the way it was in the bootstrapped project, but the build failed with exactly same errors.Also, forgot to mention, I am using sandbox env.Maybe the dependencies ar...

Hi Team, My current project is in AEM 6.5 and trying to deploy it on AEMaaCS. Our team resolved all the code related issues and code quality scan is passed as well. In the 3rd build step, while converting the project to cloud runnable image, I got below error:[ERROR] [api-regions-exportsimports] <my...