-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Quarkus generated Feature not being detected after d727a0f9fdb6bc04a7445ed77a217ce4ced2d199 #4736
Comments
This is a Quarkus issue. Quarkus tries to access The reason it only fails with the |
@christianwimmer I am wondering if the refactoring in 22.3 could be used to make |
@olpaw will work in the next weeks to add proper API for all internals that we find in Quarkus. Existing classes like |
If you like to help us with this, @zakkak, a complete list of all SVM internals used by Quarkus would be great. |
Nice. I will be out of office most of August but I believe @galderz will be able to help you with that :) |
@fniephaus We're a bit thin at the moment with people off. Didn't @christianwimmer already collect a list of SVM usages in Quarkus? He mentioned having done during the monthly call where we discussed API changes. As a FYI, following up that call I noted some of the things that seemed relevant to us in quarkusio/quarkus#25943. Issues with serialization were pointed out there too. |
Fixed in quarkusio/quarkus#26856 |
Describe the issue
d727a0f introduced a regression in Quarkus Nightly builds.
Steps to reproduce the issue
Describe GraalVM and your environment:
More details
The resulting output looks like the following:
Openning
quarkus-integration-test-main-999-SNAPSHOT-runner.jar
we see thatio.quarkus.runner.Feature
is present.It is also interesting that this class is used by other tests without any issues, e.g.,
Works as expected.
cc @peter-hofer @fniephaus
The text was updated successfully, but these errors were encountered: