Hello,
We are running into this issue with the latest version of the sonar maven plugin (5.2.0.4988), and to work around this, we would like to update the sonar project key to not match the submodule maven coordinates (e.g. com.example.group:example-artifact), by adding a prefix to the project key, e.g. mygithuborg_com.example.group:example-artifact.
However, the SonarQube Cloud UI seems to suggest that the project key should match the maven coordinates format:
Your project key is a unique identifier for your project. If you are using Maven, make sure the key matches the “groupId:artifactId” format.
Is this a hard requirement, or can we use an arbitrary project key with maven, as long as it adheres to the basic requirements?
When scanning, we pass the project key on the command line like so: -Dsonar.projectKey=…
Thanks,
Jukka