Skip to content

Conversation

@jbertram
Copy link
Contributor

@jbertram jbertram commented Jan 7, 2026

Note: this requires Maven 3.9.0 minimum (up from 3.6.3)

Note: this requires Maven 3.9.0 minimum (up from 3.6.3)
@gemmellr
Copy link
Member

A newer 37 version has been released (#6178) since changes in 36 caused issues with releasing. As the overall changes are quite numerous [1], but nothing in it seems truly needed right now (or we already overrode where needed, as you have unwound where appropriate), I think we should hold off on the change until after we release 2.50.0.

I dont think this will actually require Maven 3.9.0 as we have our own enforcer checks for Java and Maven versions overriding the parents, as its tended to lag what was wanted, and it also kept changing how theirs worked (just has again..). I do think requiring 3.9.0 makes sense though, and its now ours that is lagging, I'll have a look at updating that.

[1] apache/maven-apache-parent@apache-35...apache-37

@gemmellr gemmellr marked this pull request as draft January 14, 2026 10:30
@gemmellr
Copy link
Member

gemmellr commented Jan 14, 2026

I made the minimal update on our existing setup in 14b34424eb to bump the Maven requirement to 3.9+ before 2.50.0.

@gemmellr
Copy link
Member

We could look at removing some (we also override the java version check in the release profile, which needs to stay) of our overridden enforcement in favour of the parents. Though personally I'm not a fan of their new singular 'javaVersion' property, I much prefer the component poms having the maven compiler properties themselves (and I know of things looking for them currently) so I'd probably leave ours in place even if we use the parents enforcement checks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants