squakez commented on issue #3817:
URL: https://github.com/apache/camel-k/issues/3817#issuecomment-1319753305
I think anyhow we must rethink how we depends on the runtime. I'm drawing
some ideas and I'll submit them shortly to discuss in detail.
--
This is an automated message from the Apa
squakez commented on issue #3817:
URL: https://github.com/apache/camel-k/issues/3817#issuecomment-1319745847
Well... it seems they are already taking that path in 2.13:
https://github.com/apache/camel-quarkus/blob/2.13.x/pom.xml#L99 - they are
dropping support of Java 11 only in Native mode
squakez commented on issue #3817:
URL: https://github.com/apache/camel-k/issues/3817#issuecomment-1319729819
I guess that, as soon as Camel Quarkus switch to the new `22.3` it will need
to drop `Java 11` support as well, is that assumption right? In that case the
Camel K runtime should do t
squakez commented on issue #3817:
URL: https://github.com/apache/camel-k/issues/3817#issuecomment-1318264490
> Ah, I see. I think the native tests are failing for the same reason. Let's
wait for the latest snapshot to be available.
In theory it should be already running against the co
squakez commented on issue #3817:
URL: https://github.com/apache/camel-k/issues/3817#issuecomment-1317204963
If we run against the latest runtime snapshot, then it should be working
correctly... https://github.com/apache/camel-k-runtime/blob/main/pom.xml#L47
--
This is an automated messag
