Thomas Sapelza

I will try with a fresh WSL instance, maybe I can reproduce this also in a Linux distro.

~~I can confirm this is Windows-specific. On a fresh Windows Sandbox instance where I just set up Java and the code starter, I get the errors from the comment above...

~~So both Maven and Gradle with the Quarkus 3.12.0 code starter from above work fine under Linux. I just tried Gradle to double-check.~~ 

Nevermind, it also does not work under Linux, I just forgot to add `quarkus.native.enabled=true` for both Maven and Gradle for the Quarkus 3.12.0 AWT and REST code starter 🤦🏽‍♂️🤦🏽‍♂️🤦🏽‍♂️ It...

It also does not matter if I add `quarkus.package.jar.enabled=true`, so I have both properties set to `true`. ```properties quarkus.package.jar.enabled=true quarkus.native.enabled=true ``` https://github.com/quarkusio/quarkus/wiki/Migration-Guide-3.10#packaging-configuration-gear-white_check_mark With the Quarkus CLI 3.10.0+ migration the property...

Is this fixed in Quarkus 3.13.X?

@Trolejbus @Bock92 @cetincakiroglu the issue has been present and has been caused since the [Angular 18.2.2](https://github.com/angular/angular/releases/18.2.2) release and is unrelated to the mentioned PrimeNG 17.18.10 release. My zoneless PrimeNG application...

I see this is in active development, thank you for your work @arnoud-dv 💪🏼

This would be awesome! 🙏🏼

Sorry I already had `quarkus.rest.path` set to the following (I also updated the issue description above) and as the doc says for `quarkus.quinoa.ignored-path-prefixes`, this property automatically ignores values configured by...