JiriOndrusek opened a new pull request, #9154:
URL: https://github.com/apache/camel-quarkus/pull/9154
Fixes #9153.
`camel-kamelet` ships `DelegatingSchemaResolver`, which hard-references the
schema resolvers of the *optional* `camel-jackson`, `camel-jackson-avro` and
`camel-jackson-protobuf` dependencies. The class is the `#class:` template bean
of the catalog's `resolve-pojo-schema-action` kamelet — whenever that kamelet
is embedded into the native image (any application with the default
`quarkus.camel.kamelet.identifiers=*`), the deployment registers the class
reflectively and the GraalVM analysis fails parsing it if any of the optional
dependencies is absent: `UnresolvedElementException: NoClassDefFoundError:
org/apache/camel/component/jackson/transform/JsonSchemaResolver`.
`KameletProcessor` now removes the class from the `camel-kamelet` artifact
for native builds unless all three resolver classes are on the classpath
(`RemovedResourceBuildItem`, the `OpenaiProcessor` idiom). JVM mode is
unaffected — the class was never loadable without the optional dependencies
anyway.
Regression guard: the kamelet integration tests now embed
`resolve-pojo-schema-action` — without the fix their native build fails — and
gain a file-backed source kamelet test along the way.
Verified: kamelet integration tests green in JVM and native mode; native
fails without the fix.
_Claude Code on behalf of @JiriOndrusek_
<!-- Uncomment and fill this section if your PR is not trivial
[ ] An issue should be filed for the change unless this is a trivial change
(fixing a typo or similar). One issue should ideally be fixed by not more than
one commit and the other way round, each commit should fix just one issue,
without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful and properly
spelled subject line and body. Copying the title of the associated issue is
typically enough. Please include the issue number in the commit message
prefixed by #.
[ ] The pull request description should explain what the pull request does,
how, and why. If the info is available in the associated issue or some other
external document, a link is enough.
[ ] Phrases like Fix #<issueNumber> or Fixes #<issueNumber> will auto-close
the named issue upon merging the pull request. Using them is typically a good
idea.
[ ] Please run mvn process-resources -Pformat (and amend the changes if
necessary) before sending the pull request.
[ ] Contributor guide is your good friend:
https://camel.apache.org/camel-quarkus/latest/contributor-guide.html
-->
--
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]
