@UtilityClass -- should be non-experimental! But JavaDoc?
24 views
Skip to first unread message
Morten Sabroe Mortensen
Jul 28, 2025, 7:36:52 AMJul 28
to Project Lombok
I am extremely found of @UtilityClass. It does have value, class being marked as final, private constructor generated. There is no doubt that it has value. None whatsoever.
However, there are two issues:
1) Instead of actively marking elements, methods as static it is better to verify it and reject the existence of non-static elements. It is best to keep the keyword "static" for plain understanding.
2) JavaDoc, in general, I hope it is not specific to my setup alone, but the class is not marked "final", the constructor is public, and there is no trace of the annotation, which I guess is okay. Is it possible to have the JavaDoc tool run on the generated code?
However, there are two issues:
1) Instead of actively marking elements, methods as static it is better to verify it and reject the existence of non-static elements. It is best to keep the keyword "static" for plain understanding.
2) JavaDoc, in general, I hope it is not specific to my setup alone, but the class is not marked "final", the constructor is public, and there is no trace of the annotation, which I guess is okay. Is it possible to have the JavaDoc tool run on the generated code?
Regards,
Morten Sabroe Mortensen
Morten Sabroe Mortensen
Reply all
Reply to author
Forward
0 new messages