Sonar target configuration
Currently, the SonarQube target is the same for all Orekit forks because the
sonar.projectKey property is not defined on the Maven command line in the CI script. So the default value is used (
<groupId>:<artifactId>) and this value is the same for all Orekit forks.
The purpose of this merge request is to solve this issue by providing two additional properties on the Maven command line:
sonar.projectKey: This key is built by concatenating the values of the project namespace and the project name (separated by a colon). For instance, for my fork, the key value is
sonar.projectName: This key has been added to allow visual identification of the fork in the SonarQube interface as you can see in the screenshot below.
Warning: To enable a successful integration pipeline, you have to change the Orekit project key in SonarQube before accepting the merge request (