Set sonar-maven-plugin version to 3.3.0.603

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).

Therefore it is recommended to lock down version of Sonar plugin:
http://blog.sonatype.com/2008/04/maven-209-released/

The patch should fix honeycomb and hc2vpp merge job failures
caused by using incompatible sonar-maven-plugin version.

Change-Id: Ib95aa4a131e1b8b7d85a531bba8e5a9f7c95cf2d
Signed-off-by: Marek Gradzki <mgradzki@cisco.com>

diff --git a/common/honeycomb-parent/pom.xml b/common/honeycomb-parent/pom.xml
index 0e8e527..cc67e37 100644 (file)
--- a/common/honeycomb-parent/pom.xml
+++ b/common/honeycomb-parent/pom.xml
@@ -323,6 +323,17 @@
                         </execution>
                     </executions>
                 </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).
+                     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>
+                </plugin>
                 <!-- jacoco test coverage for sonar -->
                 <plugin>
                     <groupId>org.jacoco</groupId>