Revert "Update sonar scanner default to latest..."

This reverts commit f85c92920e00ce776ed25e70f1cd87678f2f02ab.
The commit did not have the intended effect. It was meant to replace
an outdated version of the sonar plugin, but this latest version is
not available for mvn builds. The former version is the latest
available via mvn, so we should just revert this commit. The fix for
this problem will ultimately be to update the node.js version on the
builder prior to running the scan.

Change-Id: I4acf72e50c3f54b7b49a71833bdd7648de609802
Issue-ID: CIMAN-33
Signed-off-by: Eric Ball <eball@linuxfoundation.org>

diff --git a/jjb/global-defaults.yaml b/jjb/global-defaults.yaml
index d879661..e29f278 100644 (file)
--- a/jjb/global-defaults.yaml
+++ b/jjb/global-defaults.yaml
@@ -59,7 +59,7 @@
     # SonarCloud
     sonarcloud_project_organization: onap
     sonarcloud_api_token: da97604dfdc36ec82488a97ebea96ad01f7b10ff
-    sonar_mvn_goal: "org.sonarsource.scanner.maven:sonar-maven-plugin:4.6.0.2311:sonar"
+    sonar_mvn_goal: "org.sonarsource.scanner.maven:sonar-maven-plugin:3.8.0.2131:sonar"
 
     # Nexus3 docker registries
     container-public-registry: nexus3.onap.org:10001