Add the ability to support multiple credential for multiple servers at global level
Use API from Maven SCM to validate URL instead of own implementation
This parameter is now optional for git,hg and svn
I always get the following exception :
on project example-ut-maven-jacoco-runTests: Can not execute Sonar: SCM URL must not be blank. Please check the parameter "sonar.scm.url" or the <scm> section of Maven pom
It's fixed now. I tested with projects and sub-modules, with maven and java runner.
I also added logs to tell the user what's going on during the phase where sonar is trying to guess which scm provider is used.
Works well David ! Tested with both Subversion and Git.
I really do think that with Subversion, Git and Mercurial we should no more take into account the sonar.scm.url parameter to prevent failing when this parameter is badly defined in the maven pom.xml file. I'm reopening this ticket just to be sure to have this discussion
Done. Now guessing happens before reading the url settings or the maven scm url
Manually tested !