[samson30]

Fixes debezium/dbz#1809.

Description

Standardizes the jpa-aggregations example (jpa-test and json-smt-es).

• Both modules now use debezium-examples-parent as their parent, so Java 21 and the compiler plugin version come from the root POM instead of the local Java 8 and compiler 3.8.1 settings.
• connect-json is no longer pinned to Kafka 3.4.0; its version is now managed by the Debezium BOM (4.3.1). ExpandJsonSmt only uses Connect APIs that are unchanged in Kafka 4.
• jpa-test: pins slf4j-api to 1.7.36 in dependencyManagement. The parent's BOMs manage slf4j-api 2.x, which ignores the slf4j-log4j12 1.x binding and switches SLF4J logging to NOP (same issue as in the Flink job, debezium/dbz#1809 Standardize Examples — OpenLineage Flink #496).
• CI workflow: adds actions/setup-java with Temurin 21 and fixes the Maven cache key, which pointed at apache-pulsar/**/pom.xml.
• Keeps groupId, artifactId and version unchanged, so json-smt-1.0.0.Final.jar still matches the name the Dockerfile copies.

Verification (local, compiled with release 21)

• json-smt-es: mvn clean install succeeds; connect-json, connect-api and kafka-clients resolve to 4.3.1.
• jpa-test: mvn clean test against the example's MySQL container: 4 tests, 0 failures, 0 errors. No SLF4J "no providers" warning, and Kafka's JsonConverterConfig log output is shown again.

Note

jpa-test still pins Jackson to 2.18.11, while connect-json 4.3.1 brings Jackson 2.21 modules. The tests, including the ones using JsonConverter, pass with this combination. I left the Jackson pin unchanged to keep this PR focused, but I can switch it to the BOM-managed version if you prefer.

[Naros]

Hi @samson30 let's switch to the parent POM versions for Jackson, if you don't mind.

[samson30]

Hi @samson30 let's switch to the parent POM versions for Jackson, if you don't mind.

Thanks @Naros, done. Jackson now comes from the parent's BOMs (2.21.2, so all the Jackson modules are aligned), and SLF4J uses the parent's version.slf4j. jpa-test still passes locally (4 tests, 0 failures) with no SLF4J warnings.

[Naros]

Thanks for the PR @samson30, it LGTM. I've left just one follow-up point below, if you wouldn't mind taking a look at.

[Naros]

We specifically test with JDK 21, and while Hibernate 5 appears to work with it, it isn't supported and requires at least Hibernate 6. Since Hibernate 8 is now in beta, could you raise a follow-up PR to bump this to the latest Hibernate 7.x?

[samson30]

Thanks @Naros! I will open a follow-up PR to move jpa-test to Hibernate 7.x (jakarta.persistence, org.hibernate.orm). The parent's Quarkus BOM currently manages hibernate-core 7.2.14.Final. Would you prefer I use that managed version, or pin the latest 7.x release explicitly?