From 67f70e846d6b27e219606e687c06c75527f184a5 Mon Sep 17 00:00:00 2001
From: Marek Gradzki <mgradzki@cisco.com>
Date: Mon, 13 Aug 2018 07:00:16 +0200
Subject: Bump maven-sonar-plugin version to 3.4.1.1170

Change-Id: Ic490d8b850fcd270ff49e1c682f40c0324afe3d6
Signed-off-by: Marek Gradzki <mgradzki@cisco.com>
---
 common/honeycomb-parent/pom.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/common/honeycomb-parent/pom.xml b/common/honeycomb-parent/pom.xml
index 13c669953..9e5085d0a 100644
--- a/common/honeycomb-parent/pom.xml
+++ b/common/honeycomb-parent/pom.xml
@@ -325,14 +325,14 @@
                 </plugin>
                 <!-- Sonar -->
                 <!-- If Maven encounters a plugin with no version declaration, it will use the LATEST version.
-                     which might not be compatible with Sonar server (fd.io uses 5.6 currently).
+                     which might not be compatible with Sonar server (fd.io uses 6.7.3 currently).
                      Therefore it is recommended to lock down version of Sonar plugin:
                      http://blog.sonatype.com/2008/04/maven-209-released/
                      -->
                 <plugin>
                     <groupId>org.sonarsource.scanner.maven</groupId>
                     <artifactId>sonar-maven-plugin</artifactId>
-                    <version>3.3.0.603</version>
+                    <version>3.4.1.1170</version>
                 </plugin>
                 <!-- jacoco test coverage for sonar -->
                 <plugin>
-- 
cgit 1.2.3-korg