You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by Victor Williams Stafusa da Silva <vi...@gmail.com> on 2017/11/10 18:49:03 UTC
Lombok (and perhaps other broken annotation processors) makes
Netbeans nuts.
I am an user (not a dev) of Lombok, and I'm facing issues with using Lombok
in Netbeans.
Currently, lombok do not works (at least for me) with Netbeans if using
Java 9. It does seem to work when I compile it by using Gradle at the
command line. See this:
https://github.com/rzwitserloot/lombok/issues/1435
Also, if lombok, when doing its back-magic annotation processing is able to
mess up netbeans, so something else would probably also be. Although the
lombok guys will eventually fix this issue on their side and even if it is
unfeasible to handle every case of a broken annotation processor messing
with the IDE for whichever reason, Netbeans should at least try to handle
this issue graciously.
Victor Williams Stafusa da Silva
Re: Lombok (and perhaps other broken annotation processors) makes Netbeans nuts.
Posted by Emilian Bold <em...@protonmail.ch>.
Could you share a minimal project where the bug reproduces? I don't use Gradle nor Lombok so it's kind of hard to figure how to duplicate it.
My impression is that perhaps this is a Gradle plugin bug, but I'm not certain what it hooks into.
This issue (http://statistics.netbeans.org/analytics/exception.do?id=864040 ) should be posted to https://issues.apache.org/jira/projects/NETBEANS with more details (and maybe the reproducible project I mentioned).
--emi
> -------- Original Message --------
> Subject: Re: Lombok (and perhaps other broken annotation processors) makes Netbeans nuts.
> Local Time: November 13, 2017 3:54 PM
> UTC Time: November 13, 2017 1:54 PM
> From: victorwssilva@gmail.com
> To: dev@netbeans.incubator.apache.org, Emilian Bold <em...@protonmail.ch>
>
> See the edge release. Although the original issue was something that also
> broke IntelliJ, now the edge release moved on and smacked at
> org.netbeans.modules.java.source.parsing.PatchModuleFileManager because
> some URI was not absolute. I don't know enough of internal NetBeans stuff
> to make much sense on this nor understanding what is really wrong with
> those URIs.
>
> The project that triggers the error uses Gradle for building for me, did
> not tested on anything else, but I'm considering testing that. As such,
> NetBeans do no ever shows me the "Compile On Save" option in the project
> properties.
>
> Victor Williams Stafusa da Silva
>
> 2017-11-11 3:52 GMT-02:00 Emilian Bold emilian.bold@protonmail.ch:
>
>> The issue mentions IntelliJ IDEA being also broken so it seems like a
>> general Lombok problem, not something NetBeans specific.
>> Are you using an Ant or a Maven project? Did you disable Compile On Save
>> from the project settings (as I assume this might impact Lombok
>> postprocessing)?
>> --emi
>>
>>> -------- Original Message --------
>>> Subject: Lombok (and perhaps other broken annotation processors) makes
>>> Netbeans nuts.
>>> Local Time: November 10, 2017 8:49 PM
>>> UTC Time: November 10, 2017 6:49 PM
>>> From: victorwssilva@gmail.com
>>> To: dev@netbeans.incubator.apache.org
>>> I am an user (not a dev) of Lombok, and I'm facing issues with using
>>> Lombok
>>> in Netbeans.
>>> Currently, lombok do not works (at least for me) with Netbeans if using
>>> Java 9. It does seem to work when I compile it by using Gradle at the
>>> command line. See this:
>>> https://github.com/rzwitserloot/lombok/issues/1435
>>> Also, if lombok, when doing its back-magic annotation processing is able
>>> to
>>> mess up netbeans, so something else would probably also be. Although the
>>> lombok guys will eventually fix this issue on their side and even if it
>>> is
>>> unfeasible to handle every case of a broken annotation processor messing
>>> with the IDE for whichever reason, Netbeans should at least try to handle
>>> this issue graciously.
>>> Victor Williams Stafusa da Silva
Re: Lombok (and perhaps other broken annotation processors) makes
Netbeans nuts.
Posted by Victor Williams Stafusa da Silva <vi...@gmail.com>.
See the edge release. Although the original issue was something that also
broke IntelliJ, now the edge release moved on and smacked at
org.netbeans.modules.java.source.parsing.PatchModuleFileManager because
some URI was not absolute. I don't know enough of internal NetBeans stuff
to make much sense on this nor understanding what is really wrong with
those URIs.
The project that triggers the error uses Gradle for building for me, did
not tested on anything else, but I'm considering testing that. As such,
NetBeans do no ever shows me the "Compile On Save" option in the project
properties.
Victor Williams Stafusa da Silva
2017-11-11 3:52 GMT-02:00 Emilian Bold <em...@protonmail.ch>:
> The issue mentions IntelliJ IDEA being also broken so it seems like a
> general Lombok problem, not something NetBeans specific.
>
> Are you using an Ant or a Maven project? Did you disable Compile On Save
> from the project settings (as I assume this might impact Lombok
> postprocessing)?
>
> --emi
>
> >-------- Original Message --------
> >Subject: Lombok (and perhaps other broken annotation processors) makes
> Netbeans nuts.
> >Local Time: November 10, 2017 8:49 PM
> >UTC Time: November 10, 2017 6:49 PM
> >From: victorwssilva@gmail.com
> >To: dev@netbeans.incubator.apache.org
> >
> >I am an user (not a dev) of Lombok, and I'm facing issues with using
> Lombok
> > in Netbeans.
> >
> > Currently, lombok do not works (at least for me) with Netbeans if using
> > Java 9. It does seem to work when I compile it by using Gradle at the
> > command line. See this:
> >
> >https://github.com/rzwitserloot/lombok/issues/1435
> >
> > Also, if lombok, when doing its back-magic annotation processing is able
> to
> > mess up netbeans, so something else would probably also be. Although the
> > lombok guys will eventually fix this issue on their side and even if it
> is
> > unfeasible to handle every case of a broken annotation processor messing
> > with the IDE for whichever reason, Netbeans should at least try to handle
> > this issue graciously.
> >
> > Victor Williams Stafusa da Silva
>
Re: Lombok (and perhaps other broken annotation processors) makes Netbeans nuts.
Posted by Emilian Bold <em...@protonmail.ch>.
The issue mentions IntelliJ IDEA being also broken so it seems like a general Lombok problem, not something NetBeans specific.
Are you using an Ant or a Maven project? Did you disable Compile On Save from the project settings (as I assume this might impact Lombok postprocessing)?
--emi
>-------- Original Message --------
>Subject: Lombok (and perhaps other broken annotation processors) makes Netbeans nuts.
>Local Time: November 10, 2017 8:49 PM
>UTC Time: November 10, 2017 6:49 PM
>From: victorwssilva@gmail.com
>To: dev@netbeans.incubator.apache.org
>
>I am an user (not a dev) of Lombok, and I'm facing issues with using Lombok
> in Netbeans.
>
> Currently, lombok do not works (at least for me) with Netbeans if using
> Java 9. It does seem to work when I compile it by using Gradle at the
> command line. See this:
>
>https://github.com/rzwitserloot/lombok/issues/1435
>
> Also, if lombok, when doing its back-magic annotation processing is able to
> mess up netbeans, so something else would probably also be. Although the
> lombok guys will eventually fix this issue on their side and even if it is
> unfeasible to handle every case of a broken annotation processor messing
> with the IDE for whichever reason, Netbeans should at least try to handle
> this issue graciously.
>
> Victor Williams Stafusa da Silva