gnodet commented on PR #21800:
URL: https://github.com/apache/camel/pull/21800#issuecomment-4038194230

   ## Analysis: Remaining Jackson 2 (`com.fasterxml.jackson`) Dependencies
   
   After investigating the `jackson3upgrade` branch, here's the status of 
modules still referencing `com.fasterxml.jackson.core:jackson-databind`:
   
   | Module | Jackson 2 Usage | Migration Status |
   |--------|----------------|-----------------|
   | **camel-jackson** | Core Jackson 2 data format component | **Intentional** 
— parallel `camel-jackson3` exists |
   | **camel-jacksonxml** | Core Jackson 2 XML data format component | 
**Intentional** — parallel `camel-jackson3xml` exists |
   | **camel-jslt** | `JsltEndpoint` uses `ObjectMapper`, `JsonNode` | 
**Blocked** — JSLT library (0.1.14) depends on 
`com.fasterxml.jackson.core:jackson-databind` at runtime |
   | **camel-opensearch** | `OpensearchActionRequestConverter`, 
`OpensearchProducer` | **Blocked** — OpenSearch client 3.7.0 depends on Jackson 
2 |
   | **camel-openapi-java** | `RestOpenApiSupport`, `RestModelConverters` | 
**Blocked** — Swagger libraries (`swagger-core-jakarta` 2.2.36) depend on 
Jackson 2 |
   | **camel-jbang-mcp** | No direct source code usage (test-scope deps only) | 
**Blocked** — Swagger + Quarkus transitive deps need Jackson 2 |
   
   ### Conclusion
   
   The **Jackson 2 BOM cannot be removed from `parent/pom.xml` yet**. All 
remaining Jackson 2 usages are either:
   1. **Intentional** (Jackson 2 data format components kept alongside Jackson 
3 variants), or
   2. **Blocked by upstream libraries** (JSLT, OpenSearch client, Swagger) that 
haven't released Jackson 3-compatible versions
   
   The `camel-jbang-mcp` pom already has a comment capturing this: 
_"temporarily needed until a Jackson 3 capable swagger is released"_.


-- 
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]

Reply via email to