+1 yes absolutely… I think we discussed this earlier - the only challenge I believe was that quite a few of the getters / setters actually have business logic in them, so we need to be a bit careful when introducing Lombok.
But it’s definitely doable and would remove a huge amount of the boilerplate code Regards Petri > On 16 Mar 2022, at 23:53, Awasum Yannick <[email protected]> wrote: > > +1 > > Great Idea. > > On Wed, Mar 16, 2022, 16:43 Aleksandar Vidakovic <[email protected] > <mailto:[email protected]>> wrote: > +1 > > ... very in favor of doing this... with Lombok we can also get rid of a lot > of the "@Autowired" stuff... just saying > > On Wed, Mar 16, 2022 at 2:07 PM John Woodlock <[email protected] > <mailto:[email protected]>> wrote: > Arnold, > > I'm not aware if the community has considered this or other tools for > removing Java boilercode. However, not being a native Java programmer I abhor > the Java noise. And I'm sure you'd do a great job demonstrating how Lombok > can reduce it. > > Thanks a lot > John > > On Wed, Mar 16, 2022 at 12:48 PM Arnold Galovics <[email protected] > <mailto:[email protected]>> wrote: > Dear Community, > > While I've contributed to the codebase, I realized there's a lot of > boilerplate code for a lot of classes. > Mainly, I see the constructors which are really not doing anything except > assigning parameters to fields + the @Autowired annotation. And we have a lot > of getters/setters as well, mostly on DTOs. > > I don't have a number at hand but I think by using Lombok we could reduce the > amount of boilerplate in the codebase considerably, I'm just not sure if > somebody has considered it before. > > If there's no objection, I'd start introducing it gradually and then others > could also benefit from it. > > Thoughts? > > Best, > Arnold
