jamesnetherton opened a new pull request, #3136:
URL: https://github.com/apache/camel-kamelets/pull/3136

   **Placeholder until Camel 4.24.0 is released.** This PR stays a draft until 
the catalog moves to Camel 4.24.0. The itests that need Camel 4.24 cannot pass 
before then: the kafka field actions and `resolve-pojo-schema-action`.
   
   Camel 4.24 makes Jackson 3 (`tools.jackson`) the primary Jackson line 
([CAMEL-22857](https://issues.apache.org/jira/browse/CAMEL-22857), 
apache/camel#29461). In Camel JBang the `json`, `avroJackson` and 
`protobufJackson` data formats resolve to Jackson 3, even when a Kamelet 
declares `camel:jackson`, and the `org.apache.camel.component.kafka.transform` 
classes now work on a Jackson 3 `JsonNode`. Kamelets that name Jackson 2 
classes therefore fail on Camel 4.24. The 4.24 upgrade guide lists them under 
"Jackson 3 - camel-jackson3 is the Jackson line of the catalog, Camel JBang and 
the Kamelets".
   
   Changes:
   - `camel:jackson`, `camel:jackson-avro`, `camel:jackson-protobuf` become 
`camel:jackson3`, `camel:jackson3-avro`, `camel:jackson3-protobuf`
   - `unmarshalType: com.fasterxml.jackson.databind.JsonNode` becomes 
`tools.jackson.databind.JsonNode`
   - the Avro and Protobuf schema resolver beans use the `jackson3` packages
   - the Jira Kamelets use `tools.jackson.datatype:jackson-datatype-joda`, 
versioned from the Camel `jackson3-version`
   - `azure-storage-blob-changefeed-source` drops the `JavaTimeModule` 
registration (built into Jackson 3 databind)
   - the catalog validator accepts `camel:jackson3`; the itests use 
`camel-jackson3`
   
   The kafka transform class names do not change: Camel migrated them in place.
   
   The catalog library and the Maven plugin stay on Jackson 2 (Fabric8 CRD 
model).
   
   _Claude Code on behalf of jamesnetherton_
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)


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