- SonarQube developer edition 184.108.40.206646
- SonarScanner 220.127.116.11 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?