claudio4j opened a new pull request, #5111:
URL: https://github.com/apache/camel-k/pull/5111
Fix https://github.com/apache/camel-k/issues/5099
**Release Note**
```release-note
NONE
```
--
This is an automated message from the Apache Git Servi
github-actions[bot] commented on PR #5111:
URL: https://github.com/apache/camel-k/pull/5111#issuecomment-1910805916
:heavy_check_mark: Unit test coverage report - coverage increased from 34.8%
to 35.3% (**+0.5%**)
--
This is an automated message from the Apache Git Service.
To respond to
claudio4j commented on PR #5111:
URL: https://github.com/apache/camel-k/pull/5111#issuecomment-1911819078
> We cannot hardcode variables.
This is a test only, for the catalog to be created in the
IntegrationPlatform and the status to be "Ready", it would really not matter
the versio
squakez commented on PR #5111:
URL: https://github.com/apache/camel-k/pull/5111#issuecomment-1911835525
FYI, this seems to be a regression. It was working 2 days ago:
https://github.com/apache/camel-k/actions/runs/7634756816/job/20799121558#step:4:929
--
This is an automated message from
squakez commented on PR #5111:
URL: https://github.com/apache/camel-k/pull/5111#issuecomment-1911846235
The root cause is that the new catalog has a wrong `quarkus-version`:
```
metadata:
camel-quarkus.version: 3.6.0
camel.version: 4.2.0
jib.layer-filter-e
claudio4j commented on PR #5111:
URL: https://github.com/apache/camel-k/pull/5111#issuecomment-1911920168
That version is defined in
https://github.com/apache/camel-k-runtime/blob/main/pom.xml#L46
Can you run: `make DEFAULT_RUNTIME_VERSION=3.6.0-SNAPSHOT clean build`
--
This is an
claudio4j commented on PR #5111:
URL: https://github.com/apache/camel-k/pull/5111#issuecomment-1911934177
The [nightly test
failed](https://github.com/apache/camel-k/actions/runs/7649141367/job/20843059854#step:4:1008)
exactly in the same spot.
The problem is the missing snapshot maven r
squakez commented on PR #5111:
URL: https://github.com/apache/camel-k/pull/5111#issuecomment-1911944842
IMO the problem is in the last runtime change. I'd be more inclined to
revert the latest changes there instead. At least you can confirm that one is
the root cause or this issue persist.
