[
https://issues.apache.org/jira/browse/NETBEANS-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17238812#comment-17238812
]
Xavier G commented on NETBEANS-1842:
------------------------------------
Hi again,
I rework on this issue and have found a little more information.
I try making a sample project to reproduce the issu and post it in lombok
issues list ([https://github.com/rzwitserloot/lombok/issues/2656)] but did not
succeeded to reproduce.
But doing so by looking at our original project, seems to be related to
netbeans nb-javac plugin and/or the background indexation process.
As I finally found the file generated by netbeans
(/home/user/.cache/netbeans/12.1/index/xxxxxx/myClasses.sig) corresponding to
one of my error showned in the editor (the .sig file is in fact a .class used
behind the seen by netbeans.
And if I decompile this class (with jd-gui) I note that there really are 2
methods (for each fields) with the same signature but not the same
implementation.
Exemple of what is present in this class :
```
public FilterTypeEnum getTypeFiltrage() {
throw new RuntimeException("Uncompilable source code");
}
public FilterTypeEnum getTypeFiltrage() {
return this.typeFiltrage;
}
```
Further investigation, indicate that the issue appear when reusing the sig file
by netbeans as if I delete it and netbeans regenerate it the sig file is first
OK with no error (only 1 getter/setter by fields). It's OK while I do not make
a maven compilation. When I do compile with maven (as it's a maven project) the
netbeans background scanner and external modification scanner seems to be
perturbated and that's when the bad .sig is generated.
> ambiguous method when using Lombok
> ----------------------------------
>
> Key: NETBEANS-1842
> URL: https://issues.apache.org/jira/browse/NETBEANS-1842
> Project: NetBeans
> Issue Type: Bug
> Environment: Win10
> Reporter: Rik Scarborough
> Priority: Major
> Attachments: Screen Shot 2019-07-25 at 4.14.03 PM.png
>
>
> When using lombok (v 1.18.4), generated methods show as errors in editor.
> "reference to <methodname> is ambiguous both method <methodname> in
> <classname> and method <methodname> in <classname> match".
>
> Both methodnames and classnames are the exactly same.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
