# Sonar Cloud maven multi module project jacoco aggregate code coverage not showing up **URL:** \ **Category:** SonarQube Cloud\ **Tags:** coverage\ **Created:** [July 22, 2024, 10:59pm UTC](https://community.sonarsource.com/t/sonar-cloud-maven-multi-module-project-jacoco-aggregate-code-coverage-not-showing-up/119494 "2024-07-22T22:59:31Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![Colin](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/colin/32/55255_2.png) [@Colin](https://community.sonarsource.com/u/Colin)\ **Post date:** [July 26, 2024, 8:42am UTC](https://community.sonarsource.com/t/sonar-cloud-maven-multi-module-project-jacoco-aggregate-code-coverage-not-showing-up/119494/6 "2024-07-26T08:42:01Z")
You’ll have to narrow it down to a specific discrepancy to investigate! Feel free to share an example, screenshots… > [@JaCoCo coverage is different in Sonar](https://community.sonarsource.com/t/jacoco-coverage-is-different-in-sonar/35757): > > Problem you have Your JaCoCo coverage is not the same on SonarQube/SonarCloud than it is on JaCoCo Check the following It might be expected because you are not looking at the right metrics. Read more about this in the [SonarQube and code coverage](https://community.sonarsource.com/t/sonarqube-and-code-coverage/4725) guide. Your project has more than only Java/Kotlin/Scala code so when aggregated, coverage results might differs than only Java code coverage. If you are using Lombok, make sure that you have the right configuration using the [Getting meaningful covera…](https://community.sonarsource.com/t/getting-meaningful-coverage-results-in-sonarqube-when-using-jacoco-and-lombok/13821) --- _[View the full topic](https://community.sonarsource.com/t/sonar-cloud-maven-multi-module-project-jacoco-aggregate-code-coverage-not-showing-up/119494)._