You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Steve973 <st...@gmail.com> on 2021/11/02 20:22:48 UTC
Use of lombok in camel codebase?
Hello. I normally use lombok to take care of boiler plate code in projects
that I work on. I have noticed that lombok is not used in the camel code
base. Is there something about it (licensing or something else) that makes
it unsuitable for camel? I am working on something in camel-core, and it
would be great to be able to use it to keep things cleaner. But I would
think that if it was acceptable in an apache project, people would already
be using it. Does anyone have the details on this?
Thanks,
Steve
Re: Use of lombok in camel codebase?
Posted by Andrea Cosentino <an...@gmail.com>.
So I wouldn't introduce Lombok Just for readability.
Il mar 2 nov 2021, 22:57 Andrea Cosentino <an...@gmail.com> ha scritto:
> Obviously this is my point of view, but technically,IMO, Lombok Is just a
> lot of hype with more or less zero advantages, except readability.
>
> Il mar 2 nov 2021, 22:54 Andrea Cosentino <an...@gmail.com> ha scritto:
>
>> What are you mentioning is not for free. You don't see the boilerplate,
>> but there is no magic, you'll pay this anyway. There is no good reason for
>> using Lombok and i don't feel disturbed by reading boilerplate code or
>> getter/setter
>>
>> Il mar 2 nov 2021, 22:35 Steve973 <st...@gmail.com> ha scritto:
>>
>>> You see no advantage in getting boilerplate code for free, and keeping
>>> your
>>> beans, etc, free from accessors/mutators, no arg constructors, all arg
>>> constructors, getting a builder for free, and lots of other stuff? I can
>>> see avoiding it in a project for particular reasons, but most of the
>>> "favorite" frameworks reduce a lot of boilerplate code, and Camel is
>>> included in that. I'm not arguing, but I really am curious why you see
>>> no
>>> advantage. That is, of course, if it's appropriate to have this
>>> conversation here, on this list.
>>>
>>> On Tue, Nov 2, 2021 at 5:31 PM Andrea Cosentino <an...@gmail.com>
>>> wrote:
>>>
>>> > There is no problem with license. Personally i never find any
>>> advantage in
>>> > using Lombok.
>>> >
>>> > Il mar 2 nov 2021, 21:23 Steve973 <st...@gmail.com> ha scritto:
>>> >
>>> > > Hello. I normally use lombok to take care of boiler plate code in
>>> > projects
>>> > > that I work on. I have noticed that lombok is not used in the camel
>>> code
>>> > > base. Is there something about it (licensing or something else) that
>>> > makes
>>> > > it unsuitable for camel? I am working on something in camel-core,
>>> and it
>>> > > would be great to be able to use it to keep things cleaner. But I
>>> would
>>> > > think that if it was acceptable in an apache project, people would
>>> > already
>>> > > be using it. Does anyone have the details on this?
>>> > >
>>> > > Thanks,
>>> > > Steve
>>> > >
>>> >
>>>
>>
Re: Use of lombok in camel codebase?
Posted by Andrea Cosentino <an...@gmail.com>.
Obviously this is my point of view, but technically,IMO, Lombok Is just a
lot of hype with more or less zero advantages, except readability.
Il mar 2 nov 2021, 22:54 Andrea Cosentino <an...@gmail.com> ha scritto:
> What are you mentioning is not for free. You don't see the boilerplate,
> but there is no magic, you'll pay this anyway. There is no good reason for
> using Lombok and i don't feel disturbed by reading boilerplate code or
> getter/setter
>
> Il mar 2 nov 2021, 22:35 Steve973 <st...@gmail.com> ha scritto:
>
>> You see no advantage in getting boilerplate code for free, and keeping
>> your
>> beans, etc, free from accessors/mutators, no arg constructors, all arg
>> constructors, getting a builder for free, and lots of other stuff? I can
>> see avoiding it in a project for particular reasons, but most of the
>> "favorite" frameworks reduce a lot of boilerplate code, and Camel is
>> included in that. I'm not arguing, but I really am curious why you see no
>> advantage. That is, of course, if it's appropriate to have this
>> conversation here, on this list.
>>
>> On Tue, Nov 2, 2021 at 5:31 PM Andrea Cosentino <an...@gmail.com>
>> wrote:
>>
>> > There is no problem with license. Personally i never find any advantage
>> in
>> > using Lombok.
>> >
>> > Il mar 2 nov 2021, 21:23 Steve973 <st...@gmail.com> ha scritto:
>> >
>> > > Hello. I normally use lombok to take care of boiler plate code in
>> > projects
>> > > that I work on. I have noticed that lombok is not used in the camel
>> code
>> > > base. Is there something about it (licensing or something else) that
>> > makes
>> > > it unsuitable for camel? I am working on something in camel-core,
>> and it
>> > > would be great to be able to use it to keep things cleaner. But I
>> would
>> > > think that if it was acceptable in an apache project, people would
>> > already
>> > > be using it. Does anyone have the details on this?
>> > >
>> > > Thanks,
>> > > Steve
>> > >
>> >
>>
>
Re: Use of lombok in camel codebase?
Posted by Andrea Cosentino <an...@gmail.com>.
What are you mentioning is not for free. You don't see the boilerplate, but
there is no magic, you'll pay this anyway. There is no good reason for
using Lombok and i don't feel disturbed by reading boilerplate code or
getter/setter
Il mar 2 nov 2021, 22:35 Steve973 <st...@gmail.com> ha scritto:
> You see no advantage in getting boilerplate code for free, and keeping your
> beans, etc, free from accessors/mutators, no arg constructors, all arg
> constructors, getting a builder for free, and lots of other stuff? I can
> see avoiding it in a project for particular reasons, but most of the
> "favorite" frameworks reduce a lot of boilerplate code, and Camel is
> included in that. I'm not arguing, but I really am curious why you see no
> advantage. That is, of course, if it's appropriate to have this
> conversation here, on this list.
>
> On Tue, Nov 2, 2021 at 5:31 PM Andrea Cosentino <an...@gmail.com> wrote:
>
> > There is no problem with license. Personally i never find any advantage
> in
> > using Lombok.
> >
> > Il mar 2 nov 2021, 21:23 Steve973 <st...@gmail.com> ha scritto:
> >
> > > Hello. I normally use lombok to take care of boiler plate code in
> > projects
> > > that I work on. I have noticed that lombok is not used in the camel
> code
> > > base. Is there something about it (licensing or something else) that
> > makes
> > > it unsuitable for camel? I am working on something in camel-core, and
> it
> > > would be great to be able to use it to keep things cleaner. But I
> would
> > > think that if it was acceptable in an apache project, people would
> > already
> > > be using it. Does anyone have the details on this?
> > >
> > > Thanks,
> > > Steve
> > >
> >
>
Re: Use of lombok in camel codebase?
Posted by Otavio Rodolfo Piske <an...@gmail.com>.
Personally I am not a fan of Lombok either.
I do recognize there can be some (small) convenience in using it [1].
However, I think it would be better to drive our efforts towards
modernizing the codebase to use features from newer Java versions (*when*
the time comes). Some of these features will, eventually, bring similar
convenience we see in Lombok (i.e.: Java records) at the cost of a smaller
maintenance effort.
1. https://stackoverflow.com/posts/61325018/revisions
On Thu, Nov 4, 2021 at 7:18 AM Tadayoshi Sato <sa...@gmail.com>
wrote:
> Yes, Lombok should be best for using with a Camel application, but not
> necessary so for the framework/library code of Camel itself.
> Code simplicity is great but sometimes being explicit wins over magical
> simplicity.
> As an object-oriented programmer, if we need getters/setters in the code I
> think it's already somewhat losing. Ideally we should be able to live
> without getters/setters, but if it's unavoidable then in my opinionated
> view it's less important whether it's implicit or not.
>
> On Wed, Nov 3, 2021 at 7:36 AM Vyacheslav Boyko <ma...@gmail.com>
> wrote:
>
> > Lombok have advantages and disadvantages both.
> > With bringing reducing of annoying boilerplate it brings its "magic" of
> > underlying code generation which could be understood only by having some
> > level of practice using Lobmok. For example, deserialization troubles
> > when a constructor have more than one parameter with the same type (it
> > needs to be annotated with @Creator or @ConstructorProperties). I guess,
> > the maintainers of Camel don't want to be involved into such issues.
> >
> > On 11/3/21 00:35, Steve973 wrote:
> > > You see no advantage in getting boilerplate code for free, and keeping
> > your
> > > beans, etc, free from accessors/mutators, no arg constructors, all arg
> > > constructors, getting a builder for free, and lots of other stuff? I
> can
> > > see avoiding it in a project for particular reasons, but most of the
> > > "favorite" frameworks reduce a lot of boilerplate code, and Camel is
> > > included in that. I'm not arguing, but I really am curious why you see
> > no
> > > advantage. That is, of course, if it's appropriate to have this
> > > conversation here, on this list.
> > >
> > > On Tue, Nov 2, 2021 at 5:31 PM Andrea Cosentino <an...@gmail.com>
> > wrote:
> > >
> > >> There is no problem with license. Personally i never find any
> advantage
> > in
> > >> using Lombok.
> > >>
> > >> Il mar 2 nov 2021, 21:23 Steve973 <st...@gmail.com> ha scritto:
> > >>
> > >>> Hello. I normally use lombok to take care of boiler plate code in
> > >> projects
> > >>> that I work on. I have noticed that lombok is not used in the camel
> > code
> > >>> base. Is there something about it (licensing or something else) that
> > >> makes
> > >>> it unsuitable for camel? I am working on something in camel-core,
> and
> > it
> > >>> would be great to be able to use it to keep things cleaner. But I
> > would
> > >>> think that if it was acceptable in an apache project, people would
> > >> already
> > >>> be using it. Does anyone have the details on this?
> > >>>
> > >>> Thanks,
> > >>> Steve
> > >>>
> >
>
>
> --
> Tadayoshi Sato
>
--
Otavio R. Piske
http://orpiske.net
Re: Use of lombok in camel codebase?
Posted by Tadayoshi Sato <sa...@gmail.com>.
Yes, Lombok should be best for using with a Camel application, but not
necessary so for the framework/library code of Camel itself.
Code simplicity is great but sometimes being explicit wins over magical
simplicity.
As an object-oriented programmer, if we need getters/setters in the code I
think it's already somewhat losing. Ideally we should be able to live
without getters/setters, but if it's unavoidable then in my opinionated
view it's less important whether it's implicit or not.
On Wed, Nov 3, 2021 at 7:36 AM Vyacheslav Boyko <ma...@gmail.com> wrote:
> Lombok have advantages and disadvantages both.
> With bringing reducing of annoying boilerplate it brings its "magic" of
> underlying code generation which could be understood only by having some
> level of practice using Lobmok. For example, deserialization troubles
> when a constructor have more than one parameter with the same type (it
> needs to be annotated with @Creator or @ConstructorProperties). I guess,
> the maintainers of Camel don't want to be involved into such issues.
>
> On 11/3/21 00:35, Steve973 wrote:
> > You see no advantage in getting boilerplate code for free, and keeping
> your
> > beans, etc, free from accessors/mutators, no arg constructors, all arg
> > constructors, getting a builder for free, and lots of other stuff? I can
> > see avoiding it in a project for particular reasons, but most of the
> > "favorite" frameworks reduce a lot of boilerplate code, and Camel is
> > included in that. I'm not arguing, but I really am curious why you see
> no
> > advantage. That is, of course, if it's appropriate to have this
> > conversation here, on this list.
> >
> > On Tue, Nov 2, 2021 at 5:31 PM Andrea Cosentino <an...@gmail.com>
> wrote:
> >
> >> There is no problem with license. Personally i never find any advantage
> in
> >> using Lombok.
> >>
> >> Il mar 2 nov 2021, 21:23 Steve973 <st...@gmail.com> ha scritto:
> >>
> >>> Hello. I normally use lombok to take care of boiler plate code in
> >> projects
> >>> that I work on. I have noticed that lombok is not used in the camel
> code
> >>> base. Is there something about it (licensing or something else) that
> >> makes
> >>> it unsuitable for camel? I am working on something in camel-core, and
> it
> >>> would be great to be able to use it to keep things cleaner. But I
> would
> >>> think that if it was acceptable in an apache project, people would
> >> already
> >>> be using it. Does anyone have the details on this?
> >>>
> >>> Thanks,
> >>> Steve
> >>>
>
--
Tadayoshi Sato
Re: Use of lombok in camel codebase?
Posted by Vyacheslav Boyko <ma...@gmail.com>.
Lombok have advantages and disadvantages both.
With bringing reducing of annoying boilerplate it brings its "magic" of
underlying code generation which could be understood only by having some
level of practice using Lobmok. For example, deserialization troubles
when a constructor have more than one parameter with the same type (it
needs to be annotated with @Creator or @ConstructorProperties). I guess,
the maintainers of Camel don't want to be involved into such issues.
On 11/3/21 00:35, Steve973 wrote:
> You see no advantage in getting boilerplate code for free, and keeping your
> beans, etc, free from accessors/mutators, no arg constructors, all arg
> constructors, getting a builder for free, and lots of other stuff? I can
> see avoiding it in a project for particular reasons, but most of the
> "favorite" frameworks reduce a lot of boilerplate code, and Camel is
> included in that. I'm not arguing, but I really am curious why you see no
> advantage. That is, of course, if it's appropriate to have this
> conversation here, on this list.
>
> On Tue, Nov 2, 2021 at 5:31 PM Andrea Cosentino <an...@gmail.com> wrote:
>
>> There is no problem with license. Personally i never find any advantage in
>> using Lombok.
>>
>> Il mar 2 nov 2021, 21:23 Steve973 <st...@gmail.com> ha scritto:
>>
>>> Hello. I normally use lombok to take care of boiler plate code in
>> projects
>>> that I work on. I have noticed that lombok is not used in the camel code
>>> base. Is there something about it (licensing or something else) that
>> makes
>>> it unsuitable for camel? I am working on something in camel-core, and it
>>> would be great to be able to use it to keep things cleaner. But I would
>>> think that if it was acceptable in an apache project, people would
>> already
>>> be using it. Does anyone have the details on this?
>>>
>>> Thanks,
>>> Steve
>>>
Re: Use of lombok in camel codebase?
Posted by Steve973 <st...@gmail.com>.
You see no advantage in getting boilerplate code for free, and keeping your
beans, etc, free from accessors/mutators, no arg constructors, all arg
constructors, getting a builder for free, and lots of other stuff? I can
see avoiding it in a project for particular reasons, but most of the
"favorite" frameworks reduce a lot of boilerplate code, and Camel is
included in that. I'm not arguing, but I really am curious why you see no
advantage. That is, of course, if it's appropriate to have this
conversation here, on this list.
On Tue, Nov 2, 2021 at 5:31 PM Andrea Cosentino <an...@gmail.com> wrote:
> There is no problem with license. Personally i never find any advantage in
> using Lombok.
>
> Il mar 2 nov 2021, 21:23 Steve973 <st...@gmail.com> ha scritto:
>
> > Hello. I normally use lombok to take care of boiler plate code in
> projects
> > that I work on. I have noticed that lombok is not used in the camel code
> > base. Is there something about it (licensing or something else) that
> makes
> > it unsuitable for camel? I am working on something in camel-core, and it
> > would be great to be able to use it to keep things cleaner. But I would
> > think that if it was acceptable in an apache project, people would
> already
> > be using it. Does anyone have the details on this?
> >
> > Thanks,
> > Steve
> >
>
Re: Use of lombok in camel codebase?
Posted by Andrea Cosentino <an...@gmail.com>.
There is no problem with license. Personally i never find any advantage in
using Lombok.
Il mar 2 nov 2021, 21:23 Steve973 <st...@gmail.com> ha scritto:
> Hello. I normally use lombok to take care of boiler plate code in projects
> that I work on. I have noticed that lombok is not used in the camel code
> base. Is there something about it (licensing or something else) that makes
> it unsuitable for camel? I am working on something in camel-core, and it
> would be great to be able to use it to keep things cleaner. But I would
> think that if it was acceptable in an apache project, people would already
> be using it. Does anyone have the details on this?
>
> Thanks,
> Steve
>
Re: Use of lombok in camel codebase?
Posted by Steve973 <st...@gmail.com>.
This all becomes rather moot at the moment when Claus says, "We will not
use Lombok.". It is off the table for camel. On all of our other
projects, an examination of benefits and drawbacks of Lombok is a
discussion for that team. Enjoy!
On Sun, Nov 7, 2021, 8:15 AM Otavio Rodolfo Piske <an...@gmail.com>
wrote:
> I'd be interested in hearing about these problems too.
>
> Depending on what they are and if there's enough* of those, we could even
> create some tickets on Jira to acknowledge and track the progress. It would
> certainly help to fix them - supposing it's something there's consensus
> about.
>
> On Tue, Nov 2, 2021 at 10:14 PM Andrea Cosentino <an...@gmail.com>
> wrote:
>
> > What way more issues do you see in the build?
> >
> > Il mar 2 nov 2021, 21:44 Romain Manni-Bucau <rm...@gmail.com> ha
> > scritto:
> >
> > > Hi Steve,
> > >
> > > Some ASF projects use it but the IDE setup step is reducing a bit
> > > contributions - even if I can agree camel build has way more issues -
> but
> > > since lombok is far to be mainstream - and it will be worse with java
> 17
> > -
> > > I guess it is part of the story there, but no legal issue AFAIK.
> > >
> > > Romain Manni-Bucau
> > > @rmannibucau <https://twitter.com/rmannibucau> | Blog
> > > <https://rmannibucau.metawerx.net/> | Old Blog
> > > <http://rmannibucau.wordpress.com> | Github <
> > > https://github.com/rmannibucau> |
> > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> > > <
> > >
> >
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> > > >
> > >
> > >
> > > Le mar. 2 nov. 2021 à 21:40, Steve973 <st...@gmail.com> a écrit :
> > >
> > > > Ok. Thanks, Claus. Do you mind explaining the rationale behind
> this?
> > > >
> > > > On Tue, Nov 2, 2021 at 4:39 PM Claus Ibsen <cl...@gmail.com>
> > > wrote:
> > > >
> > > > > We will not use lombock
> > > > >
> > > > >
> > > > > On Tue, 2 Nov 2021 at 21.23, Steve973 <st...@gmail.com> wrote:
> > > > >
> > > > > > Hello. I normally use lombok to take care of boiler plate code
> in
> > > > > projects
> > > > > > that I work on. I have noticed that lombok is not used in the
> > camel
> > > > code
> > > > > > base. Is there something about it (licensing or something else)
> > that
> > > > > makes
> > > > > > it unsuitable for camel? I am working on something in
> camel-core,
> > > and
> > > > it
> > > > > > would be great to be able to use it to keep things cleaner. But
> I
> > > > would
> > > > > > think that if it was acceptable in an apache project, people
> would
> > > > > already
> > > > > > be using it. Does anyone have the details on this?
> > > > > >
> > > > > > Thanks,
> > > > > > Steve
> > > > > >
> > > > > --
> > > > > Claus Ibsen
> > > > > -----------------
> > > > > http://davsclaus.com @davsclaus
> > > > > Camel in Action 2: https://www.manning.com/ibsen2
> > > > >
> > > >
> > >
> >
>
>
> --
> Otavio R. Piske
> http://orpiske.net
>
Re: Use of lombok in camel codebase?
Posted by Otavio Rodolfo Piske <an...@gmail.com>.
I'd be interested in hearing about these problems too.
Depending on what they are and if there's enough* of those, we could even
create some tickets on Jira to acknowledge and track the progress. It would
certainly help to fix them - supposing it's something there's consensus
about.
On Tue, Nov 2, 2021 at 10:14 PM Andrea Cosentino <an...@gmail.com> wrote:
> What way more issues do you see in the build?
>
> Il mar 2 nov 2021, 21:44 Romain Manni-Bucau <rm...@gmail.com> ha
> scritto:
>
> > Hi Steve,
> >
> > Some ASF projects use it but the IDE setup step is reducing a bit
> > contributions - even if I can agree camel build has way more issues - but
> > since lombok is far to be mainstream - and it will be worse with java 17
> -
> > I guess it is part of the story there, but no legal issue AFAIK.
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> | Blog
> > <https://rmannibucau.metawerx.net/> | Old Blog
> > <http://rmannibucau.wordpress.com> | Github <
> > https://github.com/rmannibucau> |
> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> > <
> >
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> > >
> >
> >
> > Le mar. 2 nov. 2021 à 21:40, Steve973 <st...@gmail.com> a écrit :
> >
> > > Ok. Thanks, Claus. Do you mind explaining the rationale behind this?
> > >
> > > On Tue, Nov 2, 2021 at 4:39 PM Claus Ibsen <cl...@gmail.com>
> > wrote:
> > >
> > > > We will not use lombock
> > > >
> > > >
> > > > On Tue, 2 Nov 2021 at 21.23, Steve973 <st...@gmail.com> wrote:
> > > >
> > > > > Hello. I normally use lombok to take care of boiler plate code in
> > > > projects
> > > > > that I work on. I have noticed that lombok is not used in the
> camel
> > > code
> > > > > base. Is there something about it (licensing or something else)
> that
> > > > makes
> > > > > it unsuitable for camel? I am working on something in camel-core,
> > and
> > > it
> > > > > would be great to be able to use it to keep things cleaner. But I
> > > would
> > > > > think that if it was acceptable in an apache project, people would
> > > > already
> > > > > be using it. Does anyone have the details on this?
> > > > >
> > > > > Thanks,
> > > > > Steve
> > > > >
> > > > --
> > > > Claus Ibsen
> > > > -----------------
> > > > http://davsclaus.com @davsclaus
> > > > Camel in Action 2: https://www.manning.com/ibsen2
> > > >
> > >
> >
>
--
Otavio R. Piske
http://orpiske.net
Re: Use of lombok in camel codebase?
Posted by Andrea Cosentino <an...@gmail.com>.
What way more issues do you see in the build?
Il mar 2 nov 2021, 21:44 Romain Manni-Bucau <rm...@gmail.com> ha
scritto:
> Hi Steve,
>
> Some ASF projects use it but the IDE setup step is reducing a bit
> contributions - even if I can agree camel build has way more issues - but
> since lombok is far to be mainstream - and it will be worse with java 17 -
> I guess it is part of the story there, but no legal issue AFAIK.
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> | Blog
> <https://rmannibucau.metawerx.net/> | Old Blog
> <http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
>
>
> Le mar. 2 nov. 2021 à 21:40, Steve973 <st...@gmail.com> a écrit :
>
> > Ok. Thanks, Claus. Do you mind explaining the rationale behind this?
> >
> > On Tue, Nov 2, 2021 at 4:39 PM Claus Ibsen <cl...@gmail.com>
> wrote:
> >
> > > We will not use lombock
> > >
> > >
> > > On Tue, 2 Nov 2021 at 21.23, Steve973 <st...@gmail.com> wrote:
> > >
> > > > Hello. I normally use lombok to take care of boiler plate code in
> > > projects
> > > > that I work on. I have noticed that lombok is not used in the camel
> > code
> > > > base. Is there something about it (licensing or something else) that
> > > makes
> > > > it unsuitable for camel? I am working on something in camel-core,
> and
> > it
> > > > would be great to be able to use it to keep things cleaner. But I
> > would
> > > > think that if it was acceptable in an apache project, people would
> > > already
> > > > be using it. Does anyone have the details on this?
> > > >
> > > > Thanks,
> > > > Steve
> > > >
> > > --
> > > Claus Ibsen
> > > -----------------
> > > http://davsclaus.com @davsclaus
> > > Camel in Action 2: https://www.manning.com/ibsen2
> > >
> >
>
Re: Use of lombok in camel codebase?
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hi Steve,
Some ASF projects use it but the IDE setup step is reducing a bit
contributions - even if I can agree camel build has way more issues - but
since lombok is far to be mainstream - and it will be worse with java 17 -
I guess it is part of the story there, but no legal issue AFAIK.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
<https://www.packtpub.com/application-development/java-ee-8-high-performance>
Le mar. 2 nov. 2021 à 21:40, Steve973 <st...@gmail.com> a écrit :
> Ok. Thanks, Claus. Do you mind explaining the rationale behind this?
>
> On Tue, Nov 2, 2021 at 4:39 PM Claus Ibsen <cl...@gmail.com> wrote:
>
> > We will not use lombock
> >
> >
> > On Tue, 2 Nov 2021 at 21.23, Steve973 <st...@gmail.com> wrote:
> >
> > > Hello. I normally use lombok to take care of boiler plate code in
> > projects
> > > that I work on. I have noticed that lombok is not used in the camel
> code
> > > base. Is there something about it (licensing or something else) that
> > makes
> > > it unsuitable for camel? I am working on something in camel-core, and
> it
> > > would be great to be able to use it to keep things cleaner. But I
> would
> > > think that if it was acceptable in an apache project, people would
> > already
> > > be using it. Does anyone have the details on this?
> > >
> > > Thanks,
> > > Steve
> > >
> > --
> > Claus Ibsen
> > -----------------
> > http://davsclaus.com @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
> >
>
Re: Use of lombok in camel codebase?
Posted by Steve973 <st...@gmail.com>.
Ok. Thanks, Claus. Do you mind explaining the rationale behind this?
On Tue, Nov 2, 2021 at 4:39 PM Claus Ibsen <cl...@gmail.com> wrote:
> We will not use lombock
>
>
> On Tue, 2 Nov 2021 at 21.23, Steve973 <st...@gmail.com> wrote:
>
> > Hello. I normally use lombok to take care of boiler plate code in
> projects
> > that I work on. I have noticed that lombok is not used in the camel code
> > base. Is there something about it (licensing or something else) that
> makes
> > it unsuitable for camel? I am working on something in camel-core, and it
> > would be great to be able to use it to keep things cleaner. But I would
> > think that if it was acceptable in an apache project, people would
> already
> > be using it. Does anyone have the details on this?
> >
> > Thanks,
> > Steve
> >
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>
Re: Use of lombok in camel codebase?
Posted by Claus Ibsen <cl...@gmail.com>.
We will not use lombock
On Tue, 2 Nov 2021 at 21.23, Steve973 <st...@gmail.com> wrote:
> Hello. I normally use lombok to take care of boiler plate code in projects
> that I work on. I have noticed that lombok is not used in the camel code
> base. Is there something about it (licensing or something else) that makes
> it unsuitable for camel? I am working on something in camel-core, and it
> would be great to be able to use it to keep things cleaner. But I would
> think that if it was acceptable in an apache project, people would already
> be using it. Does anyone have the details on this?
>
> Thanks,
> Steve
>
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2