Another round of mvn33 elimination

Previous patch missed two more instances of ovsdb-sonar's use
of maven-3.3.9. Fix them.

Change-Id: Id30e46401fbf501bfc7b0beb50dbc733a1401c9b
Signed-off-by: Robert Varga <robert.varga@pantheon.tech>

diff --git a/jjb/ovsdb/ovsdb-sonar.yaml b/jjb/ovsdb/ovsdb-sonar.yaml
index ac657e5cd5c967a6523a86f6ff19b6cd37c10b43..521a9098e420d80c916336a4fd791d38e4d7cd00 100644 (file)
--- a/jjb/ovsdb/ovsdb-sonar.yaml
+++ b/jjb/ovsdb/ovsdb-sonar.yaml
@@ -75,7 +75,7 @@
       - inject:
           properties-file: env.properties
       - maven-target:
-          maven-version: 'mvn33'
+          maven-version: 'mvn35'
           pom: 'pom.xml'
           goals: >
               verify -V -B -Pintegrationtest -Dsonar
@@ -91,7 +91,7 @@
           global-settings: 'global-settings'
           global-settings-type: cfp
       - maven-target:
-          maven-version: 'mvn33'
+          maven-version: 'mvn35'
           # We should switch to the recommended configuration of sonar once
           # JJB adds support for configurating the Sonar wrapper:
           #    http://docs.sonarqube.org/display/SCAN/Analyzing+with+SonarQube+Scanner+for+Jenkins