debezium/dbz

Standardize Java versions and adopt Debezium BOM for dependency management in debezium-examples

Open

#1,809 opened on Apr 13, 2026

View on GitHub
 (4 comments) (0 reactions) (1 assignee)HTML (6 forks)auto 404
component/examplesgood first issuetype/task

Repository metrics

Stars
 (3 stars)
PR merge metrics
 (PR metrics pending)

Description

Current Behaviour

Currently, each example in the repository uses different Java versions and manages Debezium dependencies individually. This creates several issues:

  1. Inconsistent Java versions - Examples use different maven.compiler.source/target versions (e.g., some use Java 11, others may use different versions)
  2. Manual dependency management - Each example specifies Debezium dependency versions independently, making upgrades error-prone
  3. Version conflicts - During version updates (like the recent 3.5 upgrade), incompatibility issues arise due to inconsistent dependency versions
  4. Maintenance burden - Every Debezium version upgrade requires updating multiple POMs across all examples

Expected Behaviour

  1. Standardize Java version: Choose a single Java version (e.g., Java 17 or 21) for all examples

    • Update all pom.xml files to use consistent maven.compiler.source and maven.compiler.target properties
    • Document the minimum Java version requirement in the main README

  2. Adopt Debezium BOM: Use Debezium's Bill of Materials (BOM) for dependency management

    • Import io.debezium:debezium-bom in the <dependencyManagement> section
    • Remove explicit version declarations from Debezium dependencies in individual examples
    • This ensures all Debezium components use compatible versions automatically

Related

  • debezium/dbz#1165 PR discussion

Contributor guide

Research direction
Review all example pom.xml files to identify Java compiler settings and explicit Debezium dependency versions. Determine the appropriate Debezium BOM version (matching the repository's version) and the target Java version (e.g., 17 or 21). Update the dependency management section of the parent or common POM to import the BOM, and set consistent compiler properties. Then remove explicit version from each Debezium dependency in child modules and ensure all examples build successfully.
Tech stack
java
Domain
build systemdeveloper experience
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaMavenGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70