Repository navigation
[BUG] Missing properties using @Accessors(fluent = true) in Jackson 3.0.3 #4004
Description
The following behavior changed migrating from Jackson 2.20.1 to 3.0.3. I'm using Lombok 1.18.42 and I know it's not officially supported by Jackson.
Using @Accessors(fluent = true) causes missing properties.
Let's start with a working example.
I have this class which uses Lombok annotations:
import com.fasterxml.jackson.annotation.JsonCreator;
import com.fasterxml.jackson.annotation.JsonProperty;
import lombok.Data;
@Data
public class Foo {
private String a;
private String b;
@JsonCreator
public Foo(@JsonProperty("a") final String a, @JsonProperty("b") final String b) {
this.a = a;
this.b = b;
}
}@Test
void testJacksonMigration() throws Exception {
final Foo foo = new Foo("1", "2");
final JsonMapper jsonMapper = JsonMapper.builder().build();
final String json = jsonMapper.writeValueAsString(foo);
System.out.println(json);
}prints correctly {"a":"1","b":"2"}.
If I add to Foo class "@Accessors(fluent = true)" with Jackson 3 it doesn't work anymore, so:
[...]
import lombok.experimental.Accessors;
@Data
@Accessors(fluent = true)
public class Foo {
[...]the test prints {}.
As a workaround, I added to each field a redundant @JsonProperty, but it works also with @JsonFormat, and probably any Jackson annotation.
Activity
janrieke commentedon Jan 21, 2026
I wonder why this works in Jackson 2 in the first place. It should not. Anyway, this is not a Lombok thing, it is a behavior change (probably intended) on Jackson's side.
Try adding
@Jacksonizedto the class. That should work for both Jackson 2 and 3.giacgbj commentedon Jan 22, 2026
@janrieke it works because it adds
@JsonPropertyon each field, which is the same as the workaround I found. However, it emits a warning because, as per documentation:janrieke commentedon Jan 22, 2026
It should not show that warning. Could you post the code that causes this warning?
giacgbj commentedon Jan 22, 2026
@janrieke sorry, I meant in the IDE. In IntelliJ IDEA:
feeeedox commentedon Feb 18, 2026
@janrieke
Same here!
But it's just the warning, the code is working fine after adding that.
janrieke commentedon Feb 18, 2026
Is this still an issue with the latest edge release?
feeeedox commentedon Feb 19, 2026
Yep the warning is still there.
mandrean commentedon Feb 23, 2026
Hi, I took a shot at this. Well partially, when used together with
@Jacksonized. See #4014rzwitserloot commentedon Apr 21, 2026
Fix is in, we'll push a release soon.
[changelog][#4004] Mention Jackson3 final touches in changelog.
feeeedox commentedon Apr 22, 2026
Thank you!