spuru9 opened a new pull request, #28154: URL: https://github.com/apache/flink/pull/28154
## What is the purpose of the change `flink-model-triton` pins jackson via a local `<jackson.version>` property applied uniformly to `jackson-core`, `jackson-databind`, and `jackson-annotations`. That pattern breaks at jackson 2.20+, where `jackson-annotations` decoupled from the others and stopped using patch versions on Maven Central. This PR switches the module to import `jackson-bom` instead — the same BOM already pinned at 2.21.3 in the root pom by FLINK-39580. The BOM resolves the artifacts at their correct versions automatically: `core` and `databind` at 2.21.3, `annotations` at 2.21. Resolves [FLINK-39671](https://issues.apache.org/jira/browse/FLINK-39671). ## Brief change log - `flink-models/flink-model-triton/pom.xml`: drop the `<jackson.version>` property and the per-dep `<version>${jackson.version}</version>` overrides; add `<dependencyManagement>` importing `jackson-bom` at `${jackson-bom.version}`. - `META-INF/NOTICE`: refresh to the BOM-resolved versions (`jackson-core` / `jackson-databind` 2.21.3, `jackson-annotations` 2.21). ## Verifying this change Refactor with no behavior change. Verified by: - `mvn -pl flink-models/flink-model-triton dependency:resolve` — confirms `jackson-core 2.21.3`, `jackson-databind 2.21.3`, `jackson-annotations 2.21`. - `mvn clean install -DskipTests -pl flink-models/flink-model-triton -am` builds clean. ## Does this pull request potentially affect one of the following parts: - Dependencies: **yes** (refactor only — versions move from 2.15.2 to the project-wide jackson-bom baseline) - Public API (`@Public(Evolving)`): no - Serializers: no - Runtime per-record code paths: no - Deployment/recovery — JobManager, Checkpointing, Kubernetes/Yarn, ZooKeeper: no - S3 file system connector: no ## Documentation - New feature? no --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes (Claude Code) -- 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]
