Derive Test JRE from configuration of maven-enforcer-plugin

[kwin]

Similar to what is done for the Maven Launch Configurations. Move logic for Maven Execution JRE to org.eclipse.m2e.jdt.

This closes #2059

[eclipse-m2e-bot]

This pull request changes some projects for the first time in this development cycle.
Therefore the following files need a version increment:

org.eclipse.m2e.feature/feature.xml
org.eclipse.m2e.sdk.feature/feature.xml

An additional commit containing all the necessary changes was pushed to the top of this PR's branch. To obtain these changes (for example if you want to push more changes) either fetch from your fork or apply the git patch.

Git patch

From 769fe460fa47b384ffa64996bffea5234477a007 Mon Sep 17 00:00:00 2001
From: Eclipse M2E Bot <[email protected]>
Date: Tue, 21 Oct 2025 08:42:20 +0000
Subject: [PATCH] Version bump(s) for null object or invalid expression stream


diff --git a/org.eclipse.m2e.feature/feature.xml b/org.eclipse.m2e.feature/feature.xml
index e153e1f1..b637f8d3 100644
--- a/org.eclipse.m2e.feature/feature.xml
+++ b/org.eclipse.m2e.feature/feature.xml
@@ -2,7 +2,7 @@
 <feature
       id="org.eclipse.m2e.feature"
       label="%featureName"
-      version="2.9.200.qualifier"
+      version="2.10.0.qualifier"
       provider-name="%providerName"
       plugin="org.eclipse.m2e.core"
       license-feature="org.eclipse.license"
diff --git a/org.eclipse.m2e.sdk.feature/feature.xml b/org.eclipse.m2e.sdk.feature/feature.xml
index 97dca0c3..a19f245c 100644
--- a/org.eclipse.m2e.sdk.feature/feature.xml
+++ b/org.eclipse.m2e.sdk.feature/feature.xml
@@ -2,7 +2,7 @@
 <feature
       id="org.eclipse.m2e.sdk.feature"
       label="%featureName"
-      version="2.9.200.qualifier"
+      version="2.10.0.qualifier"
       provider-name="%providerName"
       license-feature="org.eclipse.license"
       license-feature-version="0.0.0">
-- 
2.51.0

Further information are available in Common Build Issues - Missing version increments.

[github-actions]

Test Results

  327 files  +3    327 suites  +3   1h 3m 7s ⏱️ - 8m 49s
  692 tests ±0    668 ✅  - 2  21 💤 ±0  1 ❌ +1  2 🔥 +1 
2 076 runs  ±0  2 010 ✅  - 2  63 💤 ±0  1 ❌ +1  2 🔥 +1 

For more details on these failures and errors, see this check.

Results for commit a162b17. ± Comparison against base commit 27eae6a.

This pull request removes 5 and adds 5 tests. Note that renamed tests count towards both.

org.eclipse.m2e.internal.launch.MavenLaunchDelegateTest ‑ testGetBestMatchingVM_1XversionRange
org.eclipse.m2e.internal.launch.MavenLaunchDelegateTest ‑ testGetBestMatchingVM_9versionRange
org.eclipse.m2e.internal.launch.MavenLaunchDelegateTest ‑ testGetBestMatchingVM_majorOnly
org.eclipse.m2e.internal.launch.MavenLaunchDelegateTest ‑ testGetBestMatchingVM_rangeWithOnlyMajorLowerBound
org.eclipse.m2e.internal.launch.MavenLaunchDelegateTest ‑ testGetBestMatchingVM_versionRangeWithNoMajorVersionMatch

org.eclipse.m2e.jdt.tests.MavenExecutionJreTest ‑ testGetBestMatchingVM_1XversionRange
org.eclipse.m2e.jdt.tests.MavenExecutionJreTest ‑ testGetBestMatchingVM_9versionRange
org.eclipse.m2e.jdt.tests.MavenExecutionJreTest ‑ testGetBestMatchingVM_majorOnly
org.eclipse.m2e.jdt.tests.MavenExecutionJreTest ‑ testGetBestMatchingVM_rangeWithOnlyMajorLowerBound
org.eclipse.m2e.jdt.tests.MavenExecutionJreTest ‑ testGetBestMatchingVM_versionRangeWithNoMajorVersionMatch

♻️ This comment has been updated with latest results.

[kwin]

@laeubi @HannesWell Any concerns with this?