Prepare release 1.16.0

[oscerd]

Release Note

Aligning to Camel 3.19.0, Quarkus 2.14.0.Final, Quarkus Platform 2.14.0.Final and Camel-quarkus 2.14.0

All set, there is one single error in catalog. We have duplicate schemes for knative

[INFO] Running post-build script: /home/oscerd/workspace/apache-camel/camel-k-runtime/support/camel-k-maven-plugin/target/it/generate-catalog/verify.groovy
[INFO]   The post-build script did not succeed. Duplicated schemes: [knative]. Expression: (diff.size() == 0)
[INFO]           generate-catalog/pom.xml ......................... FAILED (3.0 s)

[oscerd]

@squakez @claudio4j

[squakez]

Maybe we need to remove those components originally in the runtime and now in Camel.

[oscerd]

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

[lburgazzoli]

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

[tadayosi]

As discussed at apache/camel-k#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.

[oscerd]

@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.

[squakez]

Adding @claudio4j as he did some work in Knative recently and may have some idea about the failure.

[claudio4j]

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.

[oscerd]

@zbendhiba

[oscerd]

It should be aligned now.

[oscerd]

All green. I'm going to merge.

[zbendhiba]

@claudio4j yes I migrated just one part, need to migrate the rest.