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

Deprecate usage of "sonar.profile" as an analysis parameter


    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.5.1
    • Component/s: Scanner
    • Labels:


      "sonar.profile" should not be used as an analysis parameter (i.e. set by the command line or inside the project config file) for the following reasons:

      • the profile to use should be set on the server only so that every analysis of the same project gets the same profile
      • forcing the profile on the command line can create unwanted discrepancies between several analyses
      • forcing the profile on the project config file can lead to ambiguities for those who look at the configuration on the web application (as a project admin, I set profile "Foo" but I don't see issues that I expect just because the devs have forced project "Bar" in the POM)
      • there's no guarantee that the name provided on "sonar.profile" matches an existing profile

      Since SQ 4.2 and support of multi-language projects, this property is even more ambiguous.

      For all those reasons, usage of this property should be deprecated in 4.5 LTS (with a clear message when used) so that we remove its support in a near future. This means:

      • displaying a clear warning message in the log when it is used
      • removing the documentation on the Wiki


          Issue Links



              • Assignee:
                henryju OLD - Julien HENRY
                fabemn OLD - Fabrice Bellingard
              • Votes:
                0 Vote for this issue
                20 Start watching this issue


                • Due: