-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Is there an option to exclude Jackson annotations? #2277
Comments
I'd try
No idea, if it works; you can use delombok to see the generated code. Why do you need the |
There is no way to revert to old behaviour. I need context here; I am not a user of jackson at all. Issue 2168 conflicts with what you want and I have no idea how this works. |
@rzwitserloot what kind of context do you need? I described the entire example above. Is there any option to force Lombok in newest version to not take |
That's a Jackson bug, not a lombok issue. Jackson docs say:
That is obviously not true for Besides that observation, in FasterXML/jackson-databind#1519 a Jackson developer says that it's intended that this annotation also affects serialization, so it's not the correct annotation for your use case. IMHO the JavaDoc for this annotation is misleading, I would have made the same mistake. For your usecase, Nevertheless, you should file a bug report for FasterXML/jackson-databind. |
Hi.
I have a question about my situation. I've upgraded the Lombok version in my project from 1.18.8 to 1.18.10. After this change, it started to use
@JsonSetter
values to generate fields in a JSON output. Please take a look at below example:I have a
Dog
object:In version 1.18.8 I was getting such JSON output:
while with version 1.18.10 I have:
Is there an option to have the old output with the newest version of Lombok? I found in https://projectlombok.org/changelog something like
lombok.copyableAnnotations
but as far as I see I can only add other annotations with it and not exclude some. Please advise.The text was updated successfully, but these errors were encountered: