Expand my Community achievements bar.

Submissions are now open for the 2026 Adobe Experience Maker Awards.

sonar exclusion for acs commons

Avatar

Level 1

Hello there,

 

I am trying to avoid sonar scan for third party packages/code for some reasons in cloud manager CI/CD pipeline.

 

Tried configuring below configuration in root pom file.

<properties>

        ....

        ...

        <sonar.exclusions>

           **/apps/acs-commons/**,
           **/apps/acs-commons*/**,
           **/ui.apps/src/main/content/jcr_root/apps/acs-commons/**,
           **/ui.content/src/main/content/jcr_root/apps/acs-commons/**,
           **/core/src/main/java/com/adobe/acs/**,
           **/etc/acs-commons/**
        </sonar.exclusions>
    </properties>
 
But this dint help me. Any thoughts ?. is it possible to override the pipeline so that our configuration gets priority for scanning ? or its not possible at all to avoid this scanning ?
Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Reply

Avatar

Community Advisor

Hi @PradeepMC1,

  • I think, Adobe does not use your project’s sonar.exclusions configuration by default.

  • As I know, The code quality scan in Cloud Manager is centrally controlled by Adobe and runs its own set of rules with SonarQube.

  • This means that your <sonar.exclusions> or even a custom sonar-project.properties is ignored in the Cloud Manager pipeline.

Please refer if this helps: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/sonar-s-code-scanning-conf...


Santosh Sai

AEM BlogsLinkedIn