Skip to content

chore: build against Camel 4.24.0-SNAPSHOT - #3186

Closed
davsclaus wants to merge 1 commit into
apache:mainfrom
davsclaus:quick-fix/camel-4.24.0-snapshot
Closed

davsclaus wants to merge 1 commit into
apache:mainfrom
davsclaus:quick-fix/camel-4.24.0-snapshot

Conversation

@davsclaus

@davsclaus davsclaus commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

The catalog now builds against Camel 4.24.0-SNAPSHOT instead of 4.23.0:

  • the parent camel-dependencies is now 4.24.0-SNAPSHOT;
  • camel.version is now 4.24.0-SNAPSHOT.

Why: the Kamelets can then use what Camel main adds for 4.24. The next step is the schema registry options of camel-kafka (CAMEL-27130, apache/camel#30295, merged) on the Kafka Kamelets (#3183, #3144). The build checks every Kamelet option against the Camel catalog, so a Kamelet cannot use those options while the catalog builds against 4.23.0.

What else changes:

  • Snapshot repository: the Apache snapshot repository is already configured in the pom, for dependencies and plugins.
  • SBOM: the catalog SBOM is regenerated, with the Camel components at 4.24.0-SNAPSHOT. The Catalog Dependency Scan already scans camel: components at the newest Camel release, as OSV has no data for a SNAPSHOT.
  • Integration tests: they run the Camel CLI at camel.version, which is now the 4.24.0-SNAPSHOT CLI from the snapshot repository.

Move to 4.24.0 when Camel 4.24.0 is released.

Merged together with #3136. On 4.24 the jackson data format is the Jackson 3 one whenever camel-jackson3 is on the classpath, as it is in Camel JBang. So the Kamelets must move to Jackson 3, which #3136 does. The second CI run failed 11 Citrus tests on this: json-deserialize-action and the field actions, the avro and protobuf actions, and the Jira source. The startup failure is a Camel bug, CAMEL-27164 (apache/camel#30338). Even with that fixed, the Kamelets that name the Jackson 2 JsonNode fail on the first message. #3136 is to be rebased on this branch, so CI runs both, and they merge together once it is green.

Verification:

Claude Code on behalf of Claus Ibsen

🤖 Generated with Claude Code

@davsclaus

Copy link
Copy Markdown
Contributor Author

The Integration Tests fail because of a regression in the Camel 4.24.0-SNAPSHOT CLI, not because of this PR. The snapshot itself runs fine: each integration starts as Apache Camel (JBang) 4.24.0-SNAPSHOT and reaches Running.

The failure is at the end of each test. Citrus runs camel stop <pid> with the pid of the launcher process, and the Camel JVM is a child of that process. Since 4.24, that command exits 3. Citrus then fails the test, and the integrations are left running.

The fix is CAMEL-27149, apache/camel#30321. I'll rerun the tests here once it is in a published snapshot, and hold the merge until then.

Claude Code on behalf of Claus Ibsen

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

Copy link
Copy Markdown
Contributor Author

Superseded by #3202, which has this commit together with the Jackson 3 move from #3136, both rebased on main. I'll close this one once #3202 is merged.

Claude Code on behalf of Claus Ibsen

@davsclaus

Copy link
Copy Markdown
Contributor Author

Merged as part of #3202.

Claude Code on behalf of Claus Ibsen

@davsclaus davsclaus closed this Nov 18, 2026
@davsclaus
davsclaus deleted the quick-fix/camel-4.24.0-snapshot 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.

2 participants