I think this could be a good way to improve readability of code in Malhar operators as well. This one however is MIT license. Any alternatives?
~ Bhupesh _______________________________________________________ Bhupesh Chawda Software Engineer E: [email protected] | Twitter: @bhupeshsc www.datatorrent.com | apex.apache.org On Wed, Feb 22, 2017 at 2:35 PM, Chinmay Kolhatkar <[email protected]> wrote: > Certainly good and convenient for application/operator developers to use. > > But could someone include this dependency in apex application project and > use it? > If yes, then I would prefer to keep this outside of Apex in general and let > the user use it for convenience. > > -Chinmay. > > > On Wed, Feb 22, 2017 at 2:26 PM, AJAY GUPTA <[email protected]> wrote: > > > The Java operators we write have a lot of code which is less related to > the > > business logic of the operator, eg. getters, setters, constructors, log > > variables, etc. > > Lombok library can be used to greatly avoid such code by using > annotations, > > eg. @Getter, @Setter. The library generates this code during build time. > > The code will be a lot cleaner and easier to read and develop as it will > > only contain business logic and a few annotations. > > > > PFB the links to the library features. > > https://projectlombok.org/features/index.html > > > > > > I would like to know the community views on incorporating this library > as a > > build dependency. Also, the community can decide and restrict which > > features should be allowed to be used. > > > > > > Regards, > > Ajay > > >
