Java diagnostic infer to the wrong method implem - The method X() from type Y is not visible

[ggjulio]

The java diagnostic infer the function from the wrong class/interface.
IntelliJ works fine and doesn't report any issues.

The method setValue(int, int, int) from the type A is not visible

Minimal reproduction repository : https://github.com/ggjulio/vscode-java-diagnose-bug

see examples:

• demo 1: demo-1/src/main/java/com/example/AB.java
• demo 2: demo-2/src/main/java/com/example/ABC.java

[ggjulio]

IntelliJ's code processing engine properly link to the right method in IAB interface :

Whereas VSCode point to the inherited A class:

[fbricon]

Looks like a bug in the ECJ compiler. You can try enabling the javac compiler instead in your vscode settings :

"java.jdt.ls.javac.enabled": "on"

[ggjulio]

@fbricon seem to work fine indeed with javac instead.

Repro devcontainer branch test-without-ecj-compiler

However ECJ is used in Eclipse IDE, we never had that bug in years using Eclipse IDE.

[fbricon]

@ggjulio vscode-java uses a bleeding edge version of JDT, so it might be a new regression that hasn't been published to Eclipse IDE itself. @jjohnstn can you please look into it?

[ggjulio]

@fbricon You're right, vscode-java v1.42.0 works fine

The bug is probably related to v1.43.0 changelog: https://github.com/redhat-developer/vscode-java/releases/tag/v1.43.0

[jjohnstn]

Hi @fbricon Didn't notice this yesterday, but IIRC I saw recently Stephen looking at someting similar. I'll try and reproduce and open a JDT core bug or will confirm if fixed.

[jjohnstn]

@fbricon FWIW: I tried the two example projects in my child Eclipse (I have jdt.core, jdt.debug, and jdt.ui plus some other platform classes checked out) and both work fine. The hover points to the proper setValue method and F3 brings me to the IAB interface. In my initial set-up I had jdt.core with latest commit: ea40d94dee6904e13559ab02fc9a8904922c3dc6 and my child Eclipse ran fine. I also updated master, rebuilding, and trying again. It also worked. Hopefully, your version is prior to this commit and you can refresh.

[ggjulio]

Does that mean that the bug is not anymore in upstream jdt ?

[jjohnstn]

Hopefully, your version is prior to this commit and you can refresh

What does that mean ? That the bug is not in upstream jdt and will be fixed in next vscode-java release ?

The bug is not in current upstream JDT and vscode-java releases use upstream JDT so if it hasn't been refreshed recently, then it will likely be fixed in the next release. I mentioned the commit in case the vscode-java release is current with upstream JDT in which case some further investigation would be needed. I work on upstream JDT.