Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
@Value and @FieldDefaults should skip static fields #1254
For instance fields, this makes sense. But for package private static non-final fields, this is an unexpected side-effect of adding
changed the title from
`@Value` and `@FieldDefaults` should skip static fields
@Value and @FieldDefaults should skip static fields
Dec 5, 2016
referenced this issue
Dec 5, 2016
I'm just upgrading my Lombok JAR from 1.16.10 to 1.16.16 and this "correction" just killed all my projects.
My very simple use case is to put
Now, everything is broken in all my projects and it makes Lombock useless for that kind of configuration.
Another simple use case : on my "POJO beans" (ex :
But, in fact, I use it in a "lombok.config" file to have it by default on the entire project. So I have to search for all my static fields and manually make them private where needed...
It looks like 2 little things (combined with my previous post), but in the big company I'm working for, because all the newly (last 2 years) created applications (at least a dozen) use a parent Maven dependency configuration including Lombok, that king of modification causes a not so little work to do when updating...