From afea6ad83275706eca305c4aeca872d6ea5bfc6f Mon Sep 17 00:00:00 2001 From: Robert Varga Date: Mon, 17 Dec 2018 09:54:54 +0100 Subject: [PATCH] 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 --- jjb/ovsdb/ovsdb-sonar.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/jjb/ovsdb/ovsdb-sonar.yaml b/jjb/ovsdb/ovsdb-sonar.yaml index ac657e5cd..521a9098e 100644 --- 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 -- 2.36.6