-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NPE in ConfigMapping on Native when using -H:ResourceConfigurationFiles or quarkus.native.resources.includes property #17653
Comments
cc @radcortez maybe this is related to the new |
Adding external properties on Native make the app fail to start. Reported by quarkusio/quarkus#17653
Adding external properties on Native make the app fail to start. Reported by quarkusio/quarkus#17653 sd
Adding external properties on Native make the app fail to start. Reported by quarkusio/quarkus#17653 sd
Not sure. I'll need to check. Did it work without adding the argument? |
Ok, the issue is related with the For now, you can workaround this by adding a |
The issue quarkusio/quarkus#17653 has been fixed, so we can enable the tests back. I confirmed that these tests are now working fine.
Describe the bug
Using an application that needs a resource, when registering this external resource for Native via:
pom.xml
:And:
It builds ok, but when running the Native tests or running the Native app with the next Null pointer exception:
To Reproduce
Steps to reproduce the behavior:
git clone https://github.com/Sgitario/beefy-scenarios
It fails when running the tests with the above exception.
Environment (please complete the following information):
GraalVM version (if different from Java)
GraalVM 21.0.0.2
GraalVM 21.1.0
Quarkus version or git rev
999-SNAPSHOT
The text was updated successfully, but these errors were encountered: