Drop recommendedJavaBuildVersion property

Since we use spotless for all JDK it is not needed - next simplification
mojohaus · Feb 21, 2024 · d5330b2 · d5330b2
1 parent 4fad6fe
commit d5330b2
Show file tree

Hide file tree

Showing 3 changed files with 0 additions and 8 deletions.
diff --git a/.mvn/.keep-me b/.mvn/.keep-me
diff --git a/.mvn/maven.config b/.mvn/maven.config
diff --git a/pom.xml b/pom.xml
@@ -179,8 +179,6 @@
     <maven.compiler.target>${mojo.java.target}</maven.compiler.target>
 
     <minimalJavaBuildVersion>${mojo.java.target}</minimalJavaBuildVersion>
-    <recommendedJavaBuildVersion>${minimalJavaBuildVersion}</recommendedJavaBuildVersion>
-
     <minimalMavenBuildVersion>3.6.3</minimalMavenBuildVersion>
     <mavenVersion>${minimalMavenBuildVersion}</mavenVersion>
 
@@ -656,11 +654,6 @@
                 <requireJavaVersion>
                   <version>${minimalJavaBuildVersion}</version>
                 </requireJavaVersion>
-                <requireJavaVersion>
-                  <version>${recommendedJavaBuildVersion}</version>
-                  <level>WARN</level>
-                  <message>Recommended Java version for build should be at least ${recommendedJavaBuildVersion}</message>
-                </requireJavaVersion>
                 <requireProperty>
                   <property>project.scm.connection</property>
                   <!-- because Maven adds the artifactId to the SCM-Url automatically for modules in a multimodule project,