Thomas Sapelza
Thomas Sapelza
@cetincakiroglu this is still an issue with PrimeNG v17.18.9
No @dobanisola-scottlogic it was fixed here: https://github.com/primefaces/primeng/pull/14754 See discussion https://github.com/orgs/primefaces/discussions/1136 @cetincakiroglu this issue can be closed.
@cetincakiroglu can be closed if https://github.com/primefaces/primeng/issues/14721 is done.
@cetincakiroglu this ticket can be closed, see https://github.com/primefaces/primeng/issues/14721.
Is this still planned to be worked on?
Could be fixed together with #12210
Hi @dmlloyd @geoand, the issue still persists in Quarkus 3.10.1+, the PR did not fix the issue in combination with **Quarkus AWT**. This issue was not there (also in combination...
Hello Georgios, we don't need any sophisticated reproducer, I just tried to reproduce this by downloading the following code starter https://code.quarkus.io/?g=io.quarkus&a=awt-graalvm-native-required&b=GRADLE&e=awt&e=rest&extension-search=origin:platform%20rest and set `quarkus.native.enabled=true` inside the `application.properties`, then start with...
@geoand remove your `GRAALVM_HOME` ENV var on your system, then you will get this error.
I just launched a fresh Windows 11 Sandbox, installed Eclipse Temurin 21, set the `JAVA_HOME` ENV var, and launched the Quarkus **3.12.0** code starter from above. Did you restart the...