Alexey Loubyansky

@y-luis-rojo would you be able to test a custom branch of quarkus?

It's not easy to create a proper test we could add to our testsuite for what you are seeing. I actually couldn't reproduce it but I saw other errors that...

Before I open PRs it'd be good to know whether it helps in your situation.

Excellent, here is the branch https://github.com/aloubyansky/quarkus/tree/remote-dev-delete-files-after-app-closed * `git clone [email protected]:aloubyansky/quarkus.git quarkus-remote-dev-fix` * `cd quarkus-remote-dev-fix` * `git checkout remote-dev-delete-files-after-app-closed` * `mvn -Dquickly` (this will install the `999-SNAPSHOT` version of Quarkus into...

Have you done `docker-compose down`?

Thanks a lot for testing @y-luis-rojo

This was caught in the quarkus-platform CI too. In general, we don't guarantee compatibility of specific platform member versions (e.g. CEQ 2.12.0) with core versions other than those they were...

How does it fail this time?

Let's clarify the versions. The Quarkus main branch is currently targeting 2.14 but there hasn't been a release yet. There is Quarkus 2.13 branch from which we release 2.13 versions....

Correct, CEQ stands for Camel extensions for Quarkus. Quarkus 2.14 isn't available neither. You could try building the CEQ main branch, similar to what is being done for Quarkus here.