-
Notifications
You must be signed in to change notification settings - Fork 165
De-Lombok the project #174
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
Comments
Hi @gsdatta, lombok was using to simplify development. But if this tool is problematic for Kotlin users, we can remove it :) |
Thanks @quen2404! |
@gsdatta Wouldn't this only affect you if you wanted to use the annotated POJOs as source files in your project? It should work without a problem if you're using Did you run into the problem you've described with |
@gsdatta Any additional input? |
I think I ran into this problem today in Kotlin when deserializing a full Using Spring Boot 2.3, Jackson Serialization (with Kotlin support). Example test case:
Example test output:
|
Hi, would you be open to using delombok (either at build time or on the entire codebase) from this project? Lombok makes it incompatible with Kotlin (see https://stackoverflow.com/questions/35517325/kotlin-doesnt-see-java-lombok-accessors/35530223#35530223) from the Kotlin team.
Lombok provides already a de-lombok tool https://projectlombok.org/features/delombok that could be used for this, which would then make it compatible with Kotlin.
The text was updated successfully, but these errors were encountered: