-
Notifications
You must be signed in to change notification settings - Fork 872
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
PicoCLI annotation processor not working in Kotlin/GraalVM projects #1076
Comments
Relates to #1060. |
I've just discussed that with @sdeleuze and it seems that:
|
@bclozel what is the interim solution for this? how does one configure the KAPT plugin as suggested? |
@yogeshVU I think the Picocli docs cover this: https://picocli.info/#_enabling_the_annotation_processor |
As the picocli Spring Boot starter doesn't support Boot 3.2.x or 3.3.x, we have removed it from the site. This issue is obsolete now. |
When I create a project with Kotlin, PicoCLI and GraalVM, PicoCLI's annotation processor isn't working. This annotation processor is responsible for creating the runtime hints for GraalVM. The effect is that when I run the native executable that is the result of
./gradlew nativeCompile
, I get this error:I don't know whether this is a general problem with annotation processing in Kotlin projects or if this is related to PicoCLI but I assume it's the former.
Here are reproducer projects:
To avoid having to add the runtime hints manually, I configured kapt to activate the annotation processor:
Note that kapt is in maintenance mode and superseded by KSP. I didn't take the time to look into KSP, though, as I didn't find good docs when I looked.
Kotlin/GraalVM projects generated by Initializt that need annotation processing should probably configure KSP/kapt to work properly?
The text was updated successfully, but these errors were encountered: