slachiewicz opened a new pull request, #207:
URL: https://github.com/apache/maven-dist-tool/pull/207
`<prerequisites><maven>` has reused `${mvnversion}` — the same property that
sets the `maven-core` dependency versions — since 2013. That property is now
`3.9.16`, so the declared Maven baseline has silently drifted upward with the
dependency bumps. Every other plugin in the 3.x line declares `3.6.3`.
This pins the literal `3.6.3` so the compile-time dependency and the
declared baseline move independently.
**Unlike the sibling PRs, this one changes the declared value**: `3.9.16` →
`3.6.3`, while the code still compiles against `maven-core` 3.9.16. That is the
same arrangement the rest of the estate uses (compile against current, declare
the supported baseline), but it does assume no post-3.6.3 API is in use here —
worth a second pair of eyes.
Verified with `mvn help:evaluate -Dexpression=project.prerequisites.maven` →
`3.6.3`.
<sub>Drafted with Claude — please verify</sub>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
