I honestly don’t care all that much… because I value solving real problems (that we have plenty of), rather than potential ones. But I’m not bothered either, as long as it does not negatively affect other devs and users.
On one side of the scale we have an inconvenience for those that need to upgrade Maven. It seems a small one (if it’s not for anyone reading, please let us know) but also a real one affecting, to my count so far, 4 people, including Ian,
On the other scale we have a “more predictable build”. A worth theoretical goal, but was there a practical trigger? Did you take action because someone with an old version of Maven reported build misbehaviors to you?
As a community we should strive for balance and shared decisions. Thinking out loud, how much predictability we lose if the build requires 3.8+, what would be te practical consequences of having this more relaxed check? (so far we’ve seen a comparison between not requiring a version at all, and requiring 3.9+, right?)
Cheers
Andrea