Uploaded image for project: 'SonarQube'
  1. SonarQube
  2. SONAR-4876

Allow the user to specify the key to be used for a module

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.1
    • Component/s: None
    • Labels:
      None

      Description

      Currently when sonar.projectKey is defined for a module then the resulting key of the module will be <parent key>:<sonar.projectKey>.
      This is a problem when users want to have full control on module key. This also prevent to perform a SQ analysis of a Maven project with Maven then SQ Runner. Indeed in Maven analysis module keys are <groupId>:<artifactId> without prepending parent key.

      Proposal is to introduce a new property sonar.moduleKey. When defined this property will be used verbatim as module key and sonar.projectKey will be ignored.

        Attachments

          Activity

            People

            Assignee:
            henryju OLD - Julien HENRY
            Reporter:
            henryju OLD - Julien HENRY
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Due:
              Created:
              Updated:
              Resolved: