ramackri commented on code in PR #689:
URL: https://github.com/apache/atlas/pull/689#discussion_r3526962401
##########
webapp/pom.xml:
##########
@@ -58,6 +58,18 @@
<version>${jackson.version}</version>
</dependency>
+ <dependency>
+ <groupId>com.fasterxml.jackson.jaxrs</groupId>
+ <artifactId>jackson-jaxrs-base</artifactId>
+ <version>2.12.7</version>
Review Comment:
### Jackson version split with Jersey 1.19
Atlas REST still runs on **Jersey 1.19** (JAX-RS 1.1 / JSR-311). After
bumping root `jackson.version` to **2.16.2** for Kafka 3.9.1 (PR #689), only
the **core** Jackson stack can follow that bump. **JAX-RS integration** must
stay on **2.12.7** or REST breaks (e.g. `GET /api/atlas/admin/version` did not
return 200).
| Artifact | Bump to 2.16.2 with Jersey 1.19? | Notes |
| --- | --- | --- |
| `jackson-core` / `jackson-databind` / `jackson-annotations` | **Yes** |
Already done in PR #689 — safe with Kafka 3.9 testkit and general JSON use |
| `jackson-jaxrs-base` / `jackson-jaxrs-json-provider` | **No** | Must stay
at **2.12.7** — Jersey 1.19 expects the 2.12-era JAX-RS providers
(`JacksonJaxbJsonProvider`, etc.) |
| `jsr311-api` | **N/A** (not Jackson) | Pin **1.1.1** — JAX-RS 1.1 API
required by Jersey 1.x JSON providers |
**Webapp pattern (PR #689):** exclude `jackson-jaxrs-*` from `atlas-intg`
and declare them explicitly in `webapp/pom.xml` at **2.12.7**, so the WAR gets
one known-good JAX-RS Jackson version while the rest of the build uses
**2.16.2** where Kafka requires it.
This is intentionally **not** a Jersey upgrade — it decouples server-side
JAX-RS Jackson (2.12.7) from the core Jackson bump (2.16.2).
--
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]
