davsclaus commented on PR #27206: URL: https://github.com/apache/camel/pull/27206#issuecomment-5952756452
@smongiar, thank you for digging into this. Your reproducer showed a real gap. We followed it up in #27283, which takes a different route from the one discussed here: - The root cause was that an `import` of any class of a Camel component other than the component class itself (for example `org.apache.camel.component.aws2.s3.AWS2S3Constants`, for the headers of the `aws-s3-source` Kamelet) didn't resolve. The source failed to compile before the Kamelet could load, so its `spec.dependencies` never reached the exported pom. - #27283 makes the known imports find a component by its package. The source then compiles, the Kamelet loads, and its dependencies are recorded as usual, for `camel run` as well as `camel export`. - Jackson couldn't show the problem, because the CLI always ships `camel-jackson`. A library that is neither known nor a component is still declared with `--dep`. Since #27283 covers CAMEL-25239, I suggest closing this PR in favour of it. Your report is credited in the commit and the PR. Thanks again! _Claude Code on behalf of davsclaus_ -- 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]
