[
https://issues.apache.org/jira/browse/FLINK-40629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated FLINK-40629:
-----------------------------------
Labels: pull-request-available (was: )
> Bump the build/enforced Maven version from 3.8.6 to 3.9.16 in
> flink-connector-kafka
> -----------------------------------------------------------------------------------
>
> Key: FLINK-40629
> URL: https://issues.apache.org/jira/browse/FLINK-40629
> Project: Flink
> Issue Type: Technical Debt
> Components: Connectors / Kafka
> Affects Versions: kafka-5.1.0
> Reporter: Martijn Visser
> Priority: Major
> Labels: pull-request-available
>
> flink-connector-kafka still pins Maven 3.8.6 in
> {{.mvn/wrapper/maven-wrapper.properties}}. FLINK-40459 moved Flink and
> flink-shaded to 3.9.16, so the connector should follow.
> The shared connector CI reads the version out of {{distributionUrl}} and
> hands it to setup-maven, so bumping the wrapper moves CI too.
> One thing has to land first. Maven 3.9 prints mojo banners using the plugin's
> goal prefix ({{dependency:3.8.1:tree}}) instead of its artifactId
> ({{maven-dependency-plugin:3.8.1:tree}}). flink-ci-tools' DeployParser and
> DependencyParser match only the artifactId spelling, and no released
> flink-ci-tools carries the FLINK-40459 parser fix (newest on Central is
> 2.3.0; the connector uses 2.2.1). On 3.9 the NOTICE check therefore extracts
> 0 deployed modules, demotes every NOTICE entry to a TOLERATED "not bundled,
> but listed" warning, and still exits 0. Measured locally on this repo:
> {noformat}
> Maven 3.8.6 -> Extracted 4 modules that were deployed and 7 modules which
> bundle dependencies
> Maven 3.9.16 -> Extracted 0 modules that were deployed and 7 modules which
> bundle dependencies
> {noformat}
> Both runs exit 0.
> The shared CI needs the banner-normalisation step plus an assertion on a
> non-zero module count before the wrapper here is bumped.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
