Can sonar.source dominate the SonarScanner scan path?

  • SonarQube developer edition
  • SonarScanner windows

Most of time I want to run SonarScanner in the directory other than project source directory since I run the case like publishing bullseye coverage XML report to SonarQube. While I found SonarScanner scan the current working dir for source code analysis, even though I specify -Dsonar.source=c:\otherDir to SonarScanner cmd line. So I wonder if sonar.source can dominate the path scope to SonarScanner or is there other configuration I missed?


It looked I mistype sonar.sources as sonar.sources , right? :slight_smile:

Hello @wrenaashe,

Right! the option is sonar.sources and not sonar.source.


This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.