summaryrefslogtreecommitdiffstats
path: root/common
diff options
context:
space:
mode:
authorMarek Gradzki <mgradzki@cisco.com>2018-08-13 07:00:16 +0200
committerMarek Gradzki <mgradzki@cisco.com>2018-08-13 07:00:20 +0200
commit67f70e846d6b27e219606e687c06c75527f184a5 (patch)
tree4152042d6ce154cc18a0065ae86d4e2961979cb4 /common
parentc326c58359a0ca70872f513c950effd4ed72f211 (diff)
Bump maven-sonar-plugin version to 3.4.1.1170
Change-Id: Ic490d8b850fcd270ff49e1c682f40c0324afe3d6 Signed-off-by: Marek Gradzki <mgradzki@cisco.com>
Diffstat (limited to 'common')
-rw-r--r--common/honeycomb-parent/pom.xml4
1 files changed, 2 insertions, 2 deletions
diff --git a/common/honeycomb-parent/pom.xml b/common/honeycomb-parent/pom.xml
index 13c6699..9e5085d 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>