Claus (and others),
Thank you for sharing your thoughts. I do not think any of that is harsh,
because it makes perfect logical sense, and it is what I figured. I
thought I would ask, just in case. I apologize if my questions were
annoying, and/or a waste of time. Even though I asked these
Big -1 for Lombok from me.
I fully agree with Andrea and Claus about this. Especially #4 - debugging
problems.
Saving few lines in Java code which would take you a minute to write,
comparing to seconds of lombok annotation is nothing comparing to
maintenance pain over years. Been there, done
Hi
Okay it may sound harsh when I and other long term Camel core team
members say No to X or Y.
However its a very large code base and a project that is ongoing for
decades, currently 16 and half years old.
People come and go, and it's important that everything in Camel can be
picked up and
If the component codebase is java-only, is it permissible to use test
frameworks that use other JVM languages? I am talking about things like
Spock or Kotest.
On Sun, Nov 19, 2023 at 9:21 AM Steve973 wrote:
> Oh, regarding my other question, which might have gotten lost among the
> bigger
Oh, regarding my other question, which might have gotten lost among the
bigger discussion about Lombok: is the camel component codebase java-only,
or is Kotlin also ok?
On Sun, Nov 19, 2023 at 9:20 AM Steve973 wrote:
> Thanks, Andra, for the informative reply. I understand and appreciate
>
Thanks, Andra, for the informative reply. I understand and appreciate your
assessment, and it seems like the correct decision for Apache Camel, given
your reasoning. That clears a lot of things up for me. My questions are
only out of curiosity, so I hope this discussion is reasonable and
Last but not least, there are no clear, IMO, advantages is using it,
despite the fact you'll see less boilerplate code. This laziness is
something I don't understand. IDEs will generate setters/getters for you
just with a shortcut on classes with thousands of fields.
Il giorno dom 19 nov 2023
Hello,
Let me add also add a couple of points:
1. It's true that is just a compile dependency but when you decide to use
lombok, you also decide that everyone else who deals with your code will
have to use lombok. Lombok is special in that it is a build-time dependency
and your IDE needs plugins
Does that preference extend to compile-time only, as well? The scope of
lombok is always set to "provided", so it is never included at runtime. I
am also curious if any components can be written in other JVM languages,
such as Kotlin (since camel includes the Kotlin DSL), or if it's java-only.
Hi
No lombok is not allowed - we have as minimal dependency as possible.
On Sun, Nov 19, 2023 at 2:06 PM Steve973 wrote:
> Hello. I completely understand the perspective of limiting the addition of
> libraries for various reasons, and especially when the library is included
> in the
10 matches
Mail list logo
