title: Cross-module code coverage with jacoco and gradle multi-module project
body: <p>We use gradle 3.3 and jacoco tool verson 0.7.6.201602180812.
  We have a gradle multi-project like this: </p>
  
  <ul>
  <li>parent
  
  <ul>
  <li>prod1</li>
  <li>prod2</li>
  <li>prod3</li>
  <li>int-test</li>
  </ul></li>
  </ul>
  
  <p>We use unit-tests testing the project sources and jacoco on all child-projects producing test.exec files. We have additional integration-tests in the int-test project adding jacoco results to the test-exec in the int-test project. We use sonarqube gradle plugin (2.2.1) on the parent project to collect everything for a SonarQube server v6.2. </p>
  Everything runs fine with tests that test sources in their own project: The code coverage is measured in the jacoco reports as well as on SonarQube. </p>
  Only the integration test (int-test project) coverage for the sources in the prod-projects (single process) is not measured neither in the coverage report in the project with the test nor in the project with the class. </p>
  Probably one needs to combine the coverage data on the top level project somehow - does anyone know how to do that? At best with SonarQube still showing the coverage on single module level as well.</p>
  
  <p><strong>EDIT</strong>
  Here is a small test project: <a href="https://github.com/MichaelZett/coveragetest" rel="noreferrer">https://github.com/MichaelZett/coveragetest</a>
  Running <br/>'build smokeTest sonarqube' leads to:</p>
  
  <ul>
  <li>Run of all tests</li>
  <li>producing jacoco/test.exec and test-results/test/... files in all child projects</li>
  <li>parsing of these in sonarqube</li>
  <li>correct measurement of coverage for tests that test sources in their own projects</li>
  <li>missing coverage for tests that test sources in another project</li>
  </ul>