You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The docs say that you can add a system property to workaround ksp not being compatible with allopen. However, this doesn't actually have any effect. This is a major annoyance because it's going to force us to mark all of our controllers and methods as open manually when upgrading from micronaut v3 to v4, or go back to using kapt until the ksp and allopen teams can get their stuff to play nice.
The error:
[ksp] /Users/my.user/git/my-project/src/main/kotlin/com/my/package/FooController.kt:31: Cannot apply AOP advice to final class. Class must be made non-final to support proxying: my.package.FooController
Unfortunately, KSP doesn’t see the changes in the classes made by other compiler plugins, which breaks integration with the allopen plugin. To make the integration work, we have introduced an experimental system property kotlin.allopen.annotations for the annotation processor. The property expects a list of annotations that are open, separated by ,.
Actual Behaviour
Doesn't work
Steps To Reproduce
No response
Environment Information
No response
Example Application
No response
Version
4.7.1
The text was updated successfully, but these errors were encountered:
Expected Behavior
The docs say that you can add a system property to workaround
ksp
not being compatible withallopen
. However, this doesn't actually have any effect. This is a major annoyance because it's going to force us to mark all of our controllers and methods asopen
manually when upgrading from micronaut v3 to v4, or go back to usingkapt
until theksp
andallopen
teams can get their stuff to play nice.The error:
My
gradle.properties
The docs:
Actual Behaviour
Doesn't work
Steps To Reproduce
No response
Environment Information
No response
Example Application
No response
Version
4.7.1
The text was updated successfully, but these errors were encountered: