@Value and @FieldDefaults add the private and final modifiers to the fields if possible. This behavior is influenced by @NonFinal and @PackagePrivate.
For instance fields, this makes sense. But for package private static non-final fields, this is an unexpected side-effect of adding @Value
Fixes #1254: Value and FieldDefaults should skip static fields
Would it be possible to add optional support for static fields in @FieldDefaults?