Issues using dropwizard 1.0.0-rc2 with lombok

Couple of issues I noticed, both i think were due to interactions between lombok and jackson:

1. If config classes have @AllArgsConstructor and @Builder annotation at class level, class level defaults are not prepopulated while parsing config YAML file. For example:

@Data
@NoArgsConstructor
@AllArgsConstructor
@Builder
public class TestConfig {
    @NotNull
    @NotEmpty
    private String value = "Hello";
}

//Used in config
public class MyConfig extends Configuration {
    @NotNull
    @Valid
    @Getter
    private TestConfig test = new TestConfig();
}

If the “test” section is omitted in the YAML, d/w will throw an error

1. Check the issue: https://github.com/FasterXML/jackson-databind/issues/1122

Both might be related as moving the @Builder to a clas level constructor in case 1 fixes the problem.

This breaks code written in even d/w version 0.9.2 and would seem like a critical to me.

Can jackson be upgraded before 1.0.0 release?

[ruilch]

Tested 1.0.0-rc2 with overriden jackson-databind, works fine.

[nickbabcock]

I’m optimistically assuming the problem is resolved, if not, reply back.