Introduce Maven toolchains.

This makes sure we use a Java 25+ JDK to comile,
even though the comiled code is targeted at Java 17.

Signed-off-by: Eric Bottard <eric.bottard@broadcom.com>

Author: ericbottard

pom.xml

@@ -343,7 +343,12 @@
 
 		<!-- plugin versions -->
 		<antlr.version>4.13.1</antlr.version>
-		<maven-compiler-plugin.version>3.11.0</maven-compiler-plugin.version>
+		<maven-compiler-plugin.version>3.14.1</maven-compiler-plugin.version>
+		<maven-toolchains-plugin.version>3.2.0</maven-toolchains-plugin.version>
+		<!-- The version (range) of the JDK we want to use to compile.
+			This is different from ${java.version} which we use as -release target.
+			This exact property name is recognized by the toolchains plugin. -->
+		<toolchain.jdk.version>[25,)</toolchain.jdk.version>
 		<maven-surefire-plugin.version>3.1.2</maven-surefire-plugin.version>
 		<maven-failsafe-plugin.version>3.5.2</maven-failsafe-plugin.version>
 		<maven-javadoc-plugin.version>3.5.0</maven-javadoc-plugin.version>
@@ -373,6 +378,20 @@
 
 	<build>
 		<plugins>
+			<plugin>
+				<!-- This plugin makes sure we can locate a JDK matching the ${toolchain.jdk.version} constraint.-->
+				<!-- It will be used by e.g. the maven.compiler.plugin, or fail otherwise. -->
+				<groupId>org.apache.maven.plugins</groupId>
+				<artifactId>maven-toolchains-plugin</artifactId>
+				<version>${maven-toolchains-plugin.version}</version>
+				<executions>
+					<execution>
+						<goals>
+							<goal>select-jdk-toolchain</goal>
+						</goals>
+					</execution>
+				</executions>
+			</plugin>
 			<plugin>
 				<groupId>org.apache.maven.plugins</groupId>
 				<artifactId>maven-checkstyle-plugin</artifactId>