I was waiting for an answer from the lombok team before giving further
feedback here.
I created this issue there:
https://github.com/rzwitserloot/lombok/issues/1617 and this pull request:
https://github.com/rzwitserloot/lombok/pull/1626
For me, this simple one-line fix solved the issue on
Hi Victor,
Thanks for looking at this. Some comments inline.
On Tue, Mar 13, 2018 at 12:02 AM, Victor Williams Stafusa da Silva <
victorwssi...@gmail.com> wrote:
> Anyway, independent of how much lombok finger-pointing, blaming or flaming
> we have, there seems to be something indeed
Anyway, independent of how much lombok finger-pointing, blaming or flaming
we have, there seems to be something indeed problematic in Netbeans side.
If I use Maven or Gradle to build a non-modular lombok project in Java 9,
it builds correctly afterall, but Netbeans chokes with that.
Looking at
Josh,
Try JDK 9 specifically.
The fact that they use bytecode injection makes their library very
unstable.
Gili
On Sat, Mar 10, 2018, 11:59 Josh Juneau wrote:
> I will chime in to mention that I utilize Lombok with NetBeans 8.2 and it
> works most of the time. There are
I will chime in to mention that I utilize Lombok with NetBeans 8.2 and it
works most of the time. There are some annoyances that I've noticed, but
it is most certainly due to the fact that Lombok is a compile-time
process...not a library, as mentioned in a previous thread. Typically if I
change
I have to use lombok in our Company, so it works ok but is not that Feature
rich unfortunately. I can’t refactor the getter and setter, when I added
@Getter and @Setter and Change the private variable. There is an Option while
refactoring: „Refactor getter and setter too“. But it seems not
On Fri, 9 Mar 2018 19:44:08 -0300
Victor Williams Stafusa da Silva wrote:
>
> So, what you are telling me seems to be more-or-less a great
> misunderstanding.
Mostly for others, that miss I am building everything from source. I
care more about compile time than runtime
Well, lombok is filled with eclipsy stuff because it is a parasitic
compiling tool, not a library. Keep that in mind, since many people misses
that: LOMBOK IS NOT A LIBRARY. In javac, it does its black magic by
invading javac's inner AST's. For eclipse, it is worse because it replaces
some of
On Fri, 9 Mar 2018 16:11:23 -0500
cowwoc wrote:
> I gave up using Lombok with JDK 9 months ago. Yes, it is far more
> unstable under Netbeans than with other IDEs but it is generally a
> mess under JDK9 regardless of which IDE you use.
I am not a fan of Lombok either.
I gave up using Lombok with JDK 9 months ago. Yes, it is far more
unstable under Netbeans than with other IDEs but it is generally a mess
under JDK9 regardless of which IDE you use.
Gili
On 2018-03-09 4:09 PM, Victor Williams Stafusa da Silva wrote:
Hi, I download latest Netbeans 9.0 beta
Hi, I download latest Netbeans 9.0 beta last week and I'm using with JDK 9.
My lombok projects makes Netbeans really unusable.
Those are the steps for reproducing it:
1. Create a new project.
2. Set the properties of the project to ensure that it is using JDK 9.
3. Download lombok-1.16.20.jar
11 matches
Mail list logo