Colon cannot be used in projectKey

[ragnor (Jakub)]

According to official documentation colon can be used in sonar.projectKey, by default for maven project <groupId>:<artifactId> is used as sonar.projectKey. However colon is not accepted when defining projectKey in Administration → Update Key:

Is there any way I can use colon? I have many projects already configured to use groupId:artifactId as projectKey and want to keep this convention.

[Amber (Amber vdB)]

I have the same issue. using a semicolon in a project key was never a problem before. But I cannot use it anymore for new projects

[ragnor (Jakub)]

As it was blocker for me as a temporary solution I’ve used maven property to override the default value:

<properties>
    <sonar.projectKey>my.group.my.artifact</sonar.projectKey>
</properties>

[mschmieder (Matthias Schmieder)]

This is a huge breaking change! We have setup a lot of policies and rules that match a “namespace” in the project key that is delimited with a :. Can someone clarify if this is a temporary mistake?

[edco29 (Edwin David)]

big breaking change , our team have an standardize cicd pipeline with standard project key name in the form of : $(project-name)-${groupId}:${artifact id} , this change is breaking all the scanning analysis , any thoughts why is not accepted “:”?

[mschmieder (Matthias Schmieder)]

Linking this issue:

Prevent to update project key due to unexpected characters

Hello @CommunityManagers , Currently, SonarCloud prevents updating the project key with unexpected characters (colon) [image] But the sonar plugin on Maven and Gradle automatically gets the project key with the pattern groupID:artifactName. So the colon ( is always in the project key. Now we can’t update the project key to use the Sonar Scanner plugin in Maven.

[Peter_Horvath (Peter Horváth)]

Hello,

Thank you for the feedback. We decided to revert this change for now, so : is again allowed to be used when creating/updating the project key.