Skip to content

chore: build against Camel 4.24.0-SNAPSHOT and move the Kamelets to Jackson 3 - #3202

Merged
davsclaus merged 4 commits into
apache:mainfrom
davsclaus:quick-fix/camel-4.24-jackson3
Nov 18, 2026
Merged

davsclaus merged 4 commits into
apache:mainfrom
davsclaus:quick-fix/camel-4.24-jackson3

Conversation

@davsclaus

Copy link
Copy Markdown
Contributor

Builds the catalog against Camel 4.24.0-SNAPSHOT and moves the Kamelets to Jackson 3, in one PR, because neither change passes without the other. It replaces #3186 and #3136. Their commits are kept as they were, and @jamesnetherton is still the author of the Jackson 3 commit, so please merge with "Rebase and merge".

Commits

  1. chore: build against Camel 4.24.0-SNAPSHOT (from chore: build against Camel 4.24.0-SNAPSHOT #3186, approved there). The parent camel-dependencies and camel.version are now 4.24.0-SNAPSHOT, so the Kamelets can use what Camel 4.24 adds, starting with the camel-kafka schema registry options (Kafka Kamelets: a schema registry vendor option that configures the registry for the user #3183, CAMEL-27130). The integration tests run the 4.24.0-SNAPSHOT Camel CLI.

  2. chore: move the Kamelets to Jackson 3 (camel-jackson3) (from Move the Kamelets to Jackson 3 (camel-jackson3) #3136, by James). Camel 4.24 makes Jackson 3 the primary Jackson line (CAMEL-22857):

    • camel:jackson, camel:jackson-avro and camel:jackson-protobuf become camel:jackson3, camel:jackson3-avro and camel:jackson3-protobuf;
    • unmarshalType names tools.jackson.databind.JsonNode;
    • the Avro and Protobuf schema resolvers use the jackson3 packages;
    • the Jira Kamelets use tools.jackson.datatype:jackson-datatype-joda 3.2.4;
    • the demo Kamelets in examples/kamelets get the same changes;
    • the catalog validator accepts camel:jackson3.

    The catalog library and the Maven plugin stay on Jackson 2, because the Fabric8 CRD model is Jackson 2 based.

  3. chore: regenerate the catalog SBOM. Rebasing on main conflicted only in the generated SBOM. The regenerated SBOM has the Camel components at 4.24.0-SNAPSHOT and jackson-datatype-joda 3.2.4, and no longer has the Kamelets that Fix #3180: remove the deprecated http-secured-* and jms-pooled-apache-artemis-* Kamelets #3191 removed.

  4. chore: the Avro and Protobuf itests take camel-jackson3-avro and -protobuf at the Camel version. The itests asked JBang for camel-jackson3-avro:LATEST, but LATEST resolves only released versions, and the jackson3 data formats are new in 4.24. With no version, JBang takes it from the camel-bom it imports, so it now follows the version of the Camel CLI.

Verification

  • ./mvnw clean install -DskipITs passed.
  • The Citrus tests that failed on chore: build against Camel 4.24.0-SNAPSHOT #3186 because of Jackson pass locally on Camel 4.24.0-SNAPSHOT (snapshot of 2026-11-18 09:10 UTC):
    • CommonIT: 40 tests, among them json-deserialize-action and the field actions;
    • JiraIT: 3 tests;
    • AvroIT: 2 tests;
    • ProtobufIT: 2 tests.
  • The full suite runs in CI.

The upgrade notes for the Jackson 3 move go into the Camel 4.24 upgrade guide (#3190, apache/camel#30331).

Claude Code on behalf of Claus Ibsen

🤖 Generated with Claude Code

davsclaus and others added 4 commits November 18, 2026 13:31
The parent camel-dependencies and camel.version move from 4.23.0 to
4.24.0-SNAPSHOT, so that the Kamelets can use what Camel main adds for 4.24,
such as the schema registry options of camel-kafka (CAMEL-27130) for the Kafka
Kamelets (apache#3183). The Apache snapshot repository is already configured. The
catalog SBOM is regenerated with the Camel components at 4.24.0-SNAPSHOT.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Camel 4.24 makes Jackson 3 (tools.jackson) the primary Jackson line
(CAMEL-22857), and its camel-kamelet, camel-kafka transforms and the
avro/protobuf schema resolvers move with it. Kamelets built on Jackson
follow:

- 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/protobuf schema resolver beans use the jackson3 packages
- the Jira Kamelets use tools.jackson.datatype:jackson-datatype-joda,
  now versioned from the Camel jackson3-version through the Kamelet
  version properties instead of a hardcoded 2.12.5
- azure-storage-blob-changefeed-source drops the JavaTimeModule
  registration: java.time support is built into Jackson 3 databind

The catalog validator accepts camel:jackson3 as the leading dependency,
the itests use camel-jackson3 and no longer exclude the Jackson 3
artifacts of citrus-validation-json, and the catalog SBOM is
regenerated.

The catalog library and the Maven plugin stay on Jackson 2: they parse
the Kamelet YAML through the Fabric8-generated CRD model, which is
Jackson 2 based.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…tobuf at the Camel version

LATEST resolves only released versions, and camel-jackson3-avro and
camel-jackson3-protobuf are new in Camel 4.24, so the launcher failed with
"Could not read artifact descriptor". Without a version JBang takes it from
the camel-bom it imports, which is the version of the Camel CLI.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

@jamesnetherton jamesnetherton left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Commits 1 and 2 match the changes from #3186 and #3136 that were already verified locally; the regenerated SBOM and the itest JBang dependency fix look correct, and ./mvnw clean install -DskipITs passes with no regenerated-file drift. Please merge with "Rebase and merge" as requested.

Claude Code on behalf of James Netherton

@davsclaus
davsclaus merged commit 85796d2 into apache:main Nov 18, 2026
6 checks passed
@davsclaus
davsclaus deleted the quick-fix/camel-4.24-jackson3 branch November 18, 2026 13:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants