You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default, Quarkus does not discover CDI beans outside the main module, which is the generated Camel K integration project.
For users to enable scanning of CDI beans from the integration dependencies without mandating the dependencies to provide a Jandex index, it should be possible to add quarkus.index-dependency entries for specific dependencies, as documented in:
By default, Quarkus does not discover CDI beans outside the main module, which is the generated Camel K integration project.
For users to enable scanning of CDI beans from the integration dependencies without mandating the dependencies to provide a Jandex index, it should be possible to add
quarkus.index-dependency
entries for specific dependencies, as documented in:https://quarkus.io/guides/cdi-reference#how-to-generate-a-jandex-index
The text was updated successfully, but these errors were encountered: