Fix IT failures caused by Maven 3.10.0 stricter validation level

[gnodet]

Summary

Fixes IT failures on the maven-3.10.x branch caused by stricter validation introduced in Maven 3.10.0.

Root Cause

Maven 3.10.0 changed VALIDATION_LEVEL_STRICT from VALIDATION_LEVEL_MAVEN_3_0 to VALIDATION_LEVEL_MAVEN_3_1 (commit af936f4). This promotes duplicate plugin and dependency declarations from [WARNING] to [ERROR] in strict mode.

Three ITs were broken:

Test	Failure
MavenITmng1701DuplicatePluginTest	Expected [WARNING] for duplicate plugin, got [ERROR] on Maven 3.10.x
MavenITmng4005UniqueDependencyKeyTest	Expected [WARNING] for duplicate dependency, got [ERROR] on Maven 3.10.x
MavenITmng3719PomExecutionOrderingTest	Test fixture had two separate maven-it-plugin-log-file declarations (duplicate plugin), now rejected as a validation error

Fix

• MNG-1701 / MNG-4005: Update the [WARNING] vs [ERROR] version check from (,4.0.0-alpha-1) to (,3.10.0) to correctly account for Maven 3.10.0's stricter validation level.

• MNG-3719: Merge the two separate maven-it-plugin-log-file plugin declarations in the test fixture POM into a single declaration with both executions (step 1 and step 3). The test still validates the expected execution ordering (step1 → step3 → step2). Extend the version range to include Maven 3.10.0+.

Hermes Agent (Claude Sonnet 4.6) on behalf of Guillaume Nodet

[gnodet-bot]

The fix is correct and well-reasoned. Two notes:

MNG-1701 / MNG-4005: Accepting either [WARNING] or [ERROR] is the right call. Version-boundary checks via matchesVersionRange are unreliable when the behavioral change landed after an RC (removePattern strips the qualifier, so 3.10.0-rc-1 looks like 3.10.0 to the range check). The second commit addresses exactly this.

MNG-3719 POM merge: Merging the two maven-it-plugin-log-file declarations into one is the correct fix — keeping the duplicate would just permanently fail on 3.10.0+. Worth noting that the test originally targeted the merge ordering behavior (two separate plugin declarations being merged by Maven, then run interleaved with a third plugin). After this fix, the POM has a straightforward single-declaration ordering, so the test no longer exercises merge semantics — it now just tests explicit declaration order. The assertion step1 < step3 < step2 still passes because steps 1 and 3 are declared first (under maven-it-plugin-log-file) and step 2 second (under maven-it-plugin-expression). The version range extension to [2.1.0-M2,) is correct now that the fixture is valid for all Maven versions.

This is a pragmatic fix — the original merge behavior is now an error, so the test must adapt. LGTM.

This review was generated by an AI agent, Hermès on behalf of @gnodet.