Feature request: handling protected/default fields

[GoogleCodeExporter]

I hate setters. I'd like generator to create 'with' methods for my 
package-protected fields even if there are no setters.

Please :)

Original issue reported on code.google.com by szcze...@gmail.com on 19 Jun 2010 at 6:36

[GoogleCodeExporter]

If we would allow that, we would have to search the fields, not the setters, 
and block the package choice ('cause builder would have to have the package 
access to the fields). I personally don't think that's gonna work well (for ex. 
lets consider 2 classes in different packages with package protected fields - 
we would have to generate two builders - each in different package :|)

Original comment by kube...@gmail.com on 19 Jun 2010 at 10:47

[GoogleCodeExporter]

We've rethought the idea of this - what if You could have the building 
possibilities of public fields, and if You've chosen the package that is the 
same as some of the beans in the beans graph, You additionally get the 
protected/package-protected fields ?

Original comment by kube...@gmail.com on 21 Jun 2010 at 2:14

[GoogleCodeExporter]

Original comment by kube...@gmail.com on 29 Jun 2010 at 9:48

[GoogleCodeExporter]

at first it could work with public fields, that would be nice

Original comment by tomasz.b...@pragmatists.pl on 3 Jul 2012 at 8:14

[GoogleCodeExporter]

Maybe we can merge 2 projects. I also hate setter so I create fluent builder 
generator which use reflections for private fields and java dynamic proxy. You 
can read about this here: 
https://github.com/aludwiko/fluentbuilder/wiki/Description. Or in Polish:
http://aludwikowski.blogspot.com/2013/01/fluent-builder-do-generowania-fluent_5.
html
http://aludwikowski.blogspot.com/2013/09/fluent-builder-do-generowania-fluent.ht
ml

Original comment by andrzejl...@gmail.com on 30 Sep 2013 at 4:54