Open GoogleCodeExporter opened 9 years ago
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
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
Original issue reported on code.google.com by
szcze...@gmail.com
on 19 Jun 2010 at 6:36