Jacoco in a multiple module maven project

[Kaliopa Nene]

The title may be misleading, as a current thread with that name already exists here.

But I'm facing an issues I've never seen in a forum before.

Currently I have a massive project having a similar structure:

- Project base
 - pom.xml (parent pom)
 - - - module 1

 - - - module 1 pom.xml (parent pom)

 - - - - - - module 1.2
 - - - - - - module 1.2 pom.xml (parent pom)

 - - - - - - - - - - module 1.2.1
 - - - - - - - - - - module 1.2.1 pom.xml (parent pom)
 - - - - - - - - - - module 1.2.2
 - - - - - - - - - - module 1.2.3
 - - - - - - - - - - - - - - - module 1.2.3.1
 - - - - - - - - - - - - - - - module 1.2.3.1 pom.xml (leaf pom)
 - - - - - - - - - - - - - - - module 1.2.3.2
 - - - - - - - - - - - - - - - module 1.2.3.2 pom.xml (leaf pom)
 - - - - - - - - - - - - - - - module 1.2.3.3
 - - - - - - - - - - - - - - - module 1.2.3.4

 - - - - - - module 1.3

 - - - - - - module 1.4

 - - - - - - module 1.5
 - - - module 2
 - - - module 3

I won't spam the entire project stricture as it's massive, but you get the idea - I've got a maven project, containing modules, that contain modules, containing modules.
Some of the modules are java projects, and other projects are angular ones (which will be covered with other tools).
The 'parent' modules have a 'pom' packaging, and the ones that contain the jar/war packaging are the 'leaf' projects.
There was an adoption of Cobertura, which I'm migrating from, so now I'm facing this issue:

Where and how should I create the jacoco reports, so that I can use them later for analysis

[Kaliopa Nene]

The answer lays here: https://community.sonarsource.com/t/analyze-a-multi-module-maven-project-with-angular-and-java/20422/5