Can't correctly resolve multiple @Builder methods in same class having partial implementations
See original GitHub issueIt seems that the plugin doesn’t correctly process the @Builder
annotation when it’s applied to a second method in the same class and there are already partial implementations of the builders.
Here are two screenshots of the same class with the Builder definitions inverted:




Thanks!
Issue Analytics
- State:
- Created 8 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
@Builder - Project Lombok
The @Builder annotation produces complex builder APIs for your classes. @Builder lets you automatically produce the code required to have your class be ......
Read more >java - Why do we need a Builder class when implementing a ...
Any class not knowing how to build itself is necessarily coupled to the Builder that has further dependencies (such is the purpose and...
Read more >How to create multiple varieties of a Class using the Builder ...
Effective Java suggests using parallel hierarchy of builders for such cases. Here is how abstract and concrete classes may look like:.
Read more >Reading 14: Recursion - MIT
Today's class will delve more deeply into recursion than you may have gone before. ... Let's run the recursive implementation of factorial in...
Read more >Learning the Basics - Gradle User Manual
Gradle can resolve dependencies from one or many repositories based on Maven, ... repository *only* contains artifacts with group "my.company" includeGroup ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Not sure that it’s still relevant, but I’ve encountered the same issue and resolved this by specifically setting the
builderClassName
and usage:
I’m running in to this as well with 2 different method names.