Fork JVM for SpotBugs

Downstream testing shows that parallel builds tend to hang on SpotBugs.
Run the analysis in a separate JVM again until we can figure out what is
going on.

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

diff --git a/odlparent/pom.xml b/odlparent/pom.xml
index c8e2e4674cf9e6f36b3f8922376f0a3a2017674b..970048ce9de478631eb2787c14d4be05ec0ea703 100644 (file)
--- a/odlparent/pom.xml
+++ b/odlparent/pom.xml
@@ -82,8 +82,9 @@
          to true. Set to 'false' in pom.xml of project which desires to not enforce
          no reported violations. -->
     <odlparent.spotbugs.enforce>true</odlparent.spotbugs.enforce>
-    <!-- Do not for a new JVM for spotbugs execution -->
-    <spotbugs.fork>false</spotbugs.fork>
+    <!-- Use a seaprate JVM for SpotBugs execution, as it seems to have problems in
+         parallel builds -->
+    <spotbugs.fork>true</spotbugs.fork>
 
     <!-- Opt-in into maven-dependency-plugin dependency declaration consistency
          enforcement. Defaults to false. Set to 'true' in pom.xml of a project which