From efd01b591ed73c3f5a905fbdf162a5355e586066 Mon Sep 17 00:00:00 2001
From: Michael Keppler <Michael.Keppler@gmx.de>
Date: Thu, 2 Jan 2025 15:49:25 +0100
Subject: [PATCH] Fix Maven warnings

Don't try to set maven.compiler.encoding, it's default value is
project.build.sourceEncoding, therefore that's superfluous.

Revert 296d11253931afec0b336eb1784936c4cccac4ba changes. Those are wrong
here, as tycho-surefire is not the same as maven-surefire.

Signed-off-by: Michael Keppler <Michael.Keppler@gmx.de>
---
 build/pom.xml | 10 ----------
 1 file changed, 10 deletions(-)

diff --git a/build/pom.xml b/build/pom.xml
index a5088226f..2563cbaac 100644
--- a/build/pom.xml
+++ b/build/pom.xml
@@ -34,7 +34,6 @@
          due to xtend's template symbols («) when running maven on windows. -->
     <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
     <project.build.resourceEncoding>UTF-8</project.build.resourceEncoding>
-    <maven.compiler.encoding>UTF-8</maven.compiler.encoding>
   </properties>
 
 
@@ -240,15 +239,6 @@
         <version>${tycho-version}</version>
         <configuration>
           <enableAssertions>true</enableAssertions>
-          <!-- There seems to be an issue with executing several tests in parallel in that
-               it can happen that failed tests are eventually reported as having succeeded.
-               A resolution is to set forkCount=1 and reuseForks=false
-               See, e.g. the following stackoverflow post:
-               https://stackoverflow.com/questions/3365628/junit-tests-pass-in-eclipse-but-fail-in-maven-surefire -->
-          <!-- parallel>classes</parallel -->
-          <!-- threadCount>4</threadCount -->
-          <reuseForks>false</reuseForks>
-          <forkCount>1</forkCount>
           <excludes>
             <exclude>**/TestUtil.java</exclude>
           </excludes>