You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Purushottam Sinha (Jira)" <ji...@apache.org> on 2026/05/12 18:18:00 UTC
[jira] [Created] (FLINK-39671) Adopt jackson-bom in flink-model-triton for unified version management
Purushottam Sinha created FLINK-39671:
-----------------------------------------
Summary: Adopt jackson-bom in flink-model-triton for unified version management
Key: FLINK-39671
URL: https://issues.apache.org/jira/browse/FLINK-39671
Project: Flink
Issue Type: Improvement
Components: Build System
Reporter: Purushottam Sinha
flink-model-triton declares jackson dependencies with an in-module ${jackson.version} property applied to jackson-core, jackson-databind, and jackson-annotations uniformly. This pattern breaks at jackson 2.20+, where jackson-annotations decoupled from core/databind and stopped using patch versions on Maven Central.
Proposed update:
- Drop the local <jackson.version> property and per-dep <version> overrides in flink-model-triton/pom.xml.
- Import jackson-bom (already pinned at 2.21.3 in the root pom from FLINK-39580) via <dependencyManagement>.
- BOM resolves jackson-core/databind to 2.21.3 and jackson-annotations to 2.21 — matching the project-wide baseline.
- Refresh META-INF/NOTICE to the BOM-resolved versions.
Out of scope:
Other modules that already use shaded jackson (flink-shaded-jackson) or that import the BOM directly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)