-
Notifications
You must be signed in to change notification settings - Fork 395
ShellAvailability target not registered with AOT processing #747
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
Labels
Milestone
Comments
dashaun
added a commit
to dashaun/spring-shell-bug
that referenced
this issue
May 21, 2023
As I was creating the issue, its something related to the |
ShellAvailability
results in broken build since Spring Boot 3.0.6
Thank reporting this. I'll take a look. |
Workaround is to give a hint like:
On a shell level we need to add integration to native side so that these are automatically discovered and registered. |
ShellAvailability
results in broken build since Spring Boot 3.0.6
jvalkeal
added a commit
that referenced
this issue
Jun 1, 2023
- Annotate ShellComponent with @Reflective and use custom AvailabilityReflectiveProcessor to find possible method targets returning Availability. - Backport #747 - Fixes #758
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
I noticed this when upgrading to Spring Boot 3.0.6 or 3.0.7, the build process works, but when I run the
native image
it fails.I'm using
sdkman
installedGraalVM
with identifier22.3.2.r17-grl
Steps to reproduce:
Add a custom prompt component to the class:
Optionally, replace the application.properties with application.yaml
Build the native image:
Run the image:
This is the result:
I've created an example repository here.
The text was updated successfully, but these errors were encountered: