#projectlombok — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #projectlombok, aggregated by home.social.
-
#Java records are final. They’re clean. But they can’t be extended—or can they? Discover how Froporec enables record-like inheritance via SuperRecord. Combine fields across POJOs & records—without violating JEP 395.
@ashrafbayor´s article: https://javapro.io/2025/10/07/transforming-pojos-and-java-records-with-froporec-deep-immutability-and-beyond/
-
#Java records are final. They’re clean. But they can’t be extended—or can they? Discover how Froporec enables record-like inheritance via SuperRecord. Combine fields across POJOs & records—without violating JEP 395.
@ashrafbayor´s article: https://javapro.io/2025/10/07/transforming-pojos-and-java-records-with-froporec-deep-immutability-and-beyond/
-
Tired of writing boilerplate for DTOs that should just be immutable? Froporec lets you convert POJOs into real Java records—while keeping field access, compatibility, & even collections safe.
@ashrafbayor breaks it down: https://javapro.io/2025/10/07/transforming-pojos-and-java-records-with-froporec-deep-immutability-and-beyond/
-
Tired of writing boilerplate for DTOs that should just be immutable? Froporec lets you convert POJOs into real Java records—while keeping field access, compatibility, & even collections safe.
@ashrafbayor breaks it down: https://javapro.io/2025/10/07/transforming-pojos-and-java-records-with-froporec-deep-immutability-and-beyond/
-
Need multiple immutable records—but tired of repetitive annotations? Froporec’s alsoConvert feature lets you batch-generate immutable records from multiple POJOs—using just one annotation.
Read @ashrafbayor´s story: https://javapro.io/2025/10/07/transforming-pojos-and-java-records-with-froporec-deep-immutability-and-beyond/
-
Need multiple immutable records—but tired of repetitive annotations? Froporec’s alsoConvert feature lets you batch-generate immutable records from multiple POJOs—using just one annotation.
Read @ashrafbayor´s story: https://javapro.io/2025/10/07/transforming-pojos-and-java-records-with-froporec-deep-immutability-and-beyond/
-
Mutable POJOs in critical paths? Even #Java records can't fully protect you—unless you enforce deep immutability.
Learn how Froporec turns mutable fields into unmodifiable ones—automatically. Read @ashrafbayor´s story: https://javapro.io/2025/10/07/transforming-pojos-and-java-records-with-froporec-deep-immutability-and-beyond/
-
Mutable POJOs in critical paths? Even #Java records can't fully protect you—unless you enforce deep immutability.
Learn how Froporec turns mutable fields into unmodifiable ones—automatically. Read @ashrafbayor´s story: https://javapro.io/2025/10/07/transforming-pojos-and-java-records-with-froporec-deep-immutability-and-beyond/
-
RT Payara
Java on @code Update – July 2022
@NickZhu9 @JavaAtMicrosoft tells you what's new in #VSCode for this month. #ProjectLombok support & user experience improvements. Read more:
https://hubs.ly/Q01h5zCC0:sys_twitter: https://twitter.com/Payara_Fish/status/1549393640266645508
-
Ever since I started writing #software using the #java #programming #language, I've been looking to reduce the #repetitive #boilerplate.
And I don't have a solution, yet.
Many parts of a #POJO #Bean can be auto-generated by #projectLombok, which greatly reduces the amount of logic I have to implement.
But in a suite of applications, the start of each pretty much performs the exact same operations in the exact same way, with little room to remove code duplication.
Suggestions?