While trying to test Quarkus for a personal project I’ve managed to already crash it at startup with no clear error trace, only a Process finished with exit code 1.

While trying to test Quarkus for a personal project I’ve managed to already crash it at startup with no clear error trace, only a Process finished with exit code 1.

While trying to test Quarkus for a personal project I’ve managed to already crash it at startup with no clear error trace, only a Process finished with exit code 1.

My application (gradle/quarkus) needs to specify several jvm parameters in order to function properly.

For our company, we are trying to create an extension that wraps some bussiness logic that is shared across applications.

When creating a simple quarkus app in version 3.14.2 with panache, derbydb and one entity now an error message occurs. The class ProductVersionHolder of derby-drivers is not found.

I followed a guide for implementing WebSocket extension in Quarkus. https://quarkus.io/guides/websockets

I’ve recently had a problematic non-native Quarkus service deployment to production, because one of the production profiles on the classpath application.yaml had a configuration misspelling that was only picked up when trying to start the service in production.

I’m implementing a REST-API in Quarkus and want to stream the content.

we are currently trying to upgrade from Quarkus 3.10.0 to 3.12.0