Eugene Lukash

There's `@Style(overshadowImplementation=true)` and some other attributes to tune builders. See javadocs, most such styles documented only there.

These annotations (with troubles) are TYPE_USE. so correct syntax for type use annotations (when fully qualified name involved) is `java.lang.@Nullable String nickName`, so `private @Nullable java.lang.@Nullable String nickName;` is wrong,...

is it a problem with "value-fixture" only? or other modules are affected. If this is only "value-fixture", then it can be fixed (haven't looked in those profiles in a while),...

Thats not true, this is test only artifact, noone should include it code. Those annotations you mention should be your own, create them or copy paste in your package. These...

An easy way to have forward-only builders is to use `strictBuilder`. When using strict builder, only `addAll*` and `add*` will be generated. Then actually `addAll = "*"` will bring the...

We're planning to add quite full support for records. Most probably it will be _Immutables 3_ . But there's the way now, using `@Builder.Constructor` annotation on a compact constructor. `@Builder.Constructor`...

Firstly, the conventional mechanism is when `@JsonDeserialize` is present to generate inner delegate class. I wonder if `(builder = "new")` messes up with it. Removing it might get back that...

we have something similar for importing abstract value types (as interfaces or abstract classes) from other packages, for builders alone, for those external classes which have constructors, we have `@Builder.Include()`...

I hear you, we can figure some simple solutions for these. Quick questions. Are `*IsSet()` methods (on Modifiables) are useful for anything (like checking if smth was set). What would...

`@Style(allMandatoryParameters=true)` can help you, but in for such cases / and overall small amount of fields we just stick to using with-methods. If you copy object (shallowly) couple of times...