aemanalyser-maven-plugin
aemanalyser-maven-plugin copied to clipboard
adobe
A Maven plugin used by developers who develop Java components for AEMaaCS (AEM as a Cloud Service) during their local Java builds to ensure that their components work correctly in when deployed to AEM...
[](https://renovatebot.com) Welcome to [Renovate](https://togithub.com/renovatebot/renovate)! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin. 🚦 To activate Renovate, merge this Pull Request....
![renovate[bot] avatar](https://avatars.githubusercontent.com/in/2740?v=4 "renovate[bot] avatar"){kind=avatar}
Small addendum to https://github.com/adobe/aemanalyser-maven-plugin/pull/220, issue https://github.com/adobe/aemanalyser-maven-plugin/issues/222: * https://github.com/adobe/aemanalyser-maven-plugin/pull/220 includes a content package for testing with wcm.io Handler 2.x versions, which already include a workaround for SLING-12197, by explicitly defining a...
The CMA command does not generate repoinit statements from sling initial content. These are used / required for the aem as a cloud service build, to ensure we have the...
With `aemanalyser:1.5.8:project-analyse` I get the following exception ``` [INFO] --- aemanalyser:1.5.8:project-analyse (analyser) @ novonordisk-aem-hcp-integrations-all-container --- Downloading from central: https://repo.maven.apache.org/maven2/com/adobe/aem/aemanalyser-maven-plugin/maven-metadata.xml Downloaded from central: https://repo.maven.apache.org/maven2/com/adobe/aem/aemanalyser-maven-plugin/maven-metadata.xml (1.6 kB at 15 kB/s) Downloading from...
Currently each container package is analysed separately which means that dependencies from one container content package to another is not correctly reflected in the analysis as the plugin incorrectly assumes...
A link to https://experienceleague.adobe.com/en/docs/experience-manager-core-components/using/developing/archetype/build-analyzer-maven-plugin would be helpful to have in the README for the maven plugin (https://github.com/adobe/aemanalyser-maven-plugin/blob/main/aemanalyser-maven-plugin/README.md)
Currently the plugin parameter `useDependencyVersions` is set to `false` leading to non-reproducible build (as the check is performed against a moving target). To have reproducible builds by default that parameter...
The Cloud Manager build fails (correctly) with ``` 2024-04-08 10:21:55.796 Convert Merge Analyse version [0.5.180] 2024-04-08 10:22:40.977 Analyser warnings have been found 2024-04-08 10:22:40.977 The analyser found the following warnings...
Since release 1.4.18 our maven builds fails in the analyse setup with this exception. it worked fine with 1.4.16 and below. Seems same issue was reposted some time back, but...
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....