Closed oscerd closed 1 year ago
@squakez @claudio4j
But I guess it should have been failing also on 1.15, so I'm not sure if it is coming from somewhere else. Maybe @lburgazzoli knows more
But I guess it should have been failing also on 1.15, so I'm not sure if it is coming from somewhere else. Maybe @lburgazzoli knows more
The knative extension has been introduce in camel quarkus 2.14.x, that's the only thing I know.
@zbendhiba may know more
As discussed at https://github.com/apache/camel-k/issues/3817, there's currently an issue with native builds for Camel K due to the version of ubi-quarkus-native-image
in the camel-k-runtime.
@squakez @lburgazzoli @zbendhiba
I removed the camel-k-knative stuff from camel-k-runtime and pointing only to camel-quarkus-knative. Locally I still have failing itests related to knative.
Adding @claudio4j as he did some work in Knative recently and may have some idea about the failure.
It seems not all camel-k-knative were migrated to camel-quarkus, the impl
module functionality is not there, specifically this @LoaderInterceptor("knative-source") which is failing.
@zbendhiba
It should be aligned now.
All green. I'm going to merge.
@claudio4j yes I migrated just one part, need to migrate the rest.
Release Note
All set, there is one single error in catalog. We have duplicate schemes for knative