Runtime trait failure

[squakez]

When we use -t camel.runtime-version property, the Integration got stuck and doesn't run.

$ kamel run /tmp/Hello.java --dev -x test -t camel.runtime-version=1.13.0
Integration "hello" created
Condition "IntegrationPlatformAvailable" is "True" for Integration hello: default/test
Progress: integration "hello" in phase Initialization
Integration "hello" in phase "Initialization"
Progress: integration "hello" in phase Building Kit
Integration "hello" in phase "Building Kit"
Condition "IntegrationKitAvailable" is "False" for Integration hello: creating a new integration kit
Integration Kit "kit-cd8h447viejc73dj81fg", created by Integration "hello", changed phase to "Build Submitted"
Build "kit-cd8h447viejc73dj81fg", created by Integration "hello", changed phase to "Scheduling"
Build "kit-cd8h447viejc73dj81fg", created by Integration "hello", changed phase to "Pending"
Build "kit-cd8h447viejc73dj81fg", created by Integration "hello", changed phase to "Running"
Integration Kit "kit-cd8h447viejc73dj81fg", created by Integration "hello", changed phase to "Build Running"
Build "kit-cd8h447viejc73dj81fg", created by Integration "hello", changed phase to "Succeeded"
Integration Kit "kit-cd8h447viejc73dj81fg", created by Integration "hello", changed phase to "Ready"

[squakez]

Th problem seems to be the non propagation of traits to IntegrationKit and Build when they are not declared as annotations. If we use annotations, then we have another kind of error.

[tadayosi]

Th problem seems to be the non propagation of traits to IntegrationKit and Build when they are not declared as annotations. If we use annotations, then we have another kind of error.

I'm curious about the issue. Probably it's because right now only Builder, Quarkus, and Registry are possible kit traits while Camel trait is not.

[squakez]

Great hint @tadayosi. Indeed, the problem was related to the fact the trait was not included for the Kit.