-
Notifications
You must be signed in to change notification settings - Fork 601
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
StateMachineConfigBuilder not compatible with Spring Boot 3.0 Native image AOT processing #1080
Comments
There is a pull request for upgrading to 3 (#1104). |
That pull request is closed, but as of today, 20 December 2023, this error is still happening with Spring AOT processing. |
This is Spring boot 3.2.0 and statemachine 4.0.0, by the way. |
I see this error in Spring boot 3.2.2 as well.
|
SpringBoot3.2.5 still . ____ _ __ _ _ 2024-05-16T10:49:17.134+08:00 INFO 12340 --- [ main] c.w.ln.WorldtechLnApplicationTests : Starting WorldtechLnApplicationTests using Java 17.0.11 with PID 12340 (started by 18721 in D:\Project\idea\worldtech-ln) . ____ _ __ _ _ 2024-05-16T10:49:19.747+08:00 INFO 9320 --- [ main] c.worldtech.ln.WorldtechLnApplication : Starting WorldtechLnApplication using Java 17.0.11 with PID 9320 (D:\Project\idea\worldtech-ln\target\classes started by 18721 in D:\Project\idea\worldtech-ln) |
这是来自QQ邮箱的假期自动回复邮件。
您好,我最近正在休假中,无法亲自回复您的邮件。我将在假期结束后,尽快给您回复。
|
Spring Boot 3.0 brings support for native image creation.
I've recently upgraded my project, which implements spring-statemachine-core 3.2.0, to Spring Boot 3.0 and was eager to try out the new native image creation. However, when I run
mvn spring-boot:process-aot
, I get the following error:I've tried downgrading and switching versions of Spring SM but I get the same error every time. Are projects that use Spring SM not intended to be used along with GraalVM native?
I've tried downgrading and switching versions of Spring SM but I get the same error every time. Are projects that use Spring SM not intended to be used along with GraalVM native?
The text was updated successfully, but these errors were encountered: