This is an automated email from the ASF dual-hosted git repository.
jamesnetherton pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git
The following commit(s) were added to refs/heads/main by this push:
new 5322552539 chore: document that Camel components ship with Jandex index
5322552539 is described below
commit 5322552539f0c3a8ba3b3e6e6039f3c122b45058
Author: James Netherton <[email protected]>
AuthorDate: Mon Jun 22 11:23:17 2026 +0100
chore: document that Camel components ship with Jandex index
Add a note to the native build troubleshooting section clarifying that
Camel component JARs already include a Jandex index, so
IndexDependencyBuildItem should not be added for them.
Co-authored-by: Claude Opus 4.6 (1M context) <[email protected]>
---
AGENTS.md | 2 ++
1 file changed, 2 insertions(+)
diff --git a/AGENTS.md b/AGENTS.md
index 7105cf6c7d..08c98dcd86 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -216,6 +216,8 @@ Native compilation with GraalVM requires explicit
registration of classes, resou
Use `CombinedIndexBuildItem` to discover classes at build time — see
`extensions/servicenow/deployment/.../ServicenowProcessor.java`.
+**Camel components already ship with a Jandex index.** Do not add
`IndexDependencyBuildItem` for Camel component JARs (e.g. `camel-a2a`,
`camel-kafka`). `CombinedIndexBuildItem` can discover their classes directly.
Only add `IndexDependencyBuildItem` for non-Camel third-party libraries that
lack a Jandex index.
+
See also https://quarkus.io/guides/writing-extensions.
## Security Model
