Hi all, I'd like to propose moving Flink's build from the currently pinned Maven 3.8.6 to the Maven 3.9 line (3.9.16). This was left for "a separate discussion" when we adopted Apache Parent POM 35 in FLINK-39427 [1]
I'd propose to move it because: - Maven 3.8.6 (2022) is aging; 3.9.x is the current stable 3.x line and a prerequisite for future Apache Parent POM upgrades (36+). - It moves us onto Maven's "consumer POM" model behavior that anticipates Maven 4. I've ran a sample/local red/green diff of 3.8.6 version 3.9.16, building flink-s3-fs-hadoop -am on JDK 17 and 11, the full flink-dist -am reactor on JDK 17, and a -Prelease build on Java 11 to match how releases are actually cut. Both are building cleanly on JDK 17 and 11, the shaded uber-jars seem to be byte-identical in contents and the aggregated NOTICE files also seem identical, except the manifest "Created-By" changes. The only change I saw is that the flink-parent pom inlines the release profile plugin config, while 3.9 emits the pom with re-inlining them. Perhaps there will be more issues when opening a PR, but from a first glance it seemed to be OK locally. While running the tests I did see that there is a warning about gpgArguments, which now surfaces. I'll file a separate Jira on this, it's because of the maven-gpg-plugin version we're using. Thanks, Martijn [1] https://issues.apache.org/jira/browse/FLINK-39427
