You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
step 3: "import the project in vscode"
open MyCustomizer.java and select the method called customize
make a right click and select Show call hierarchy
Vscode should (and do) find a method (see screenshot)
step 4: open pom.xml and uncomment the dependency:
step 5:
open MyCustomizer.java and select the method called customize
make a right click and select Show call hierarchy
--> VSCODE does not find any calls to this method: that is an error! vscode should find the same call hierarchy as on step 3 (IntelliJ shows correctly the call hierarchy)
The text was updated successfully, but these errors were encountered:
Thanks for the example. I'm able to reproduce this with VS Code and with Eclipse as well, so could be an issue with JDT. Likely an upstream issue.
I tried a simple example to confirm that calling some interface's method, should result in all implementations showing the implemented method as having been referenced once (or have an entry pointing to the usage in the call hierarchy).
The guava library includes the $EnumUtils class that breaks the Call Hierrachy action. The class contains a reference to a potential customize method.
I have created eclipse-jdt/eclipse.jdt.core#670
A workaround:
Environment
Steps To Reproduce
I have created a public repo so that the issue is easily reproducible:
step1: clone this repo:
step2: run
mvn clean install
step 3: "import the project in vscode"
open
MyCustomizer.java
and select the method calledcustomize
make a right click and select
Show call hierarchy
Vscode should (and do) find a method (see screenshot)
step 4: open
pom.xml
and uncomment the dependency:step 5:
open
MyCustomizer.java
and select the method calledcustomize
make a right click and select
Show call hierarchy
--> VSCODE does not find any calls to this method: that is an error! vscode should find the same call hierarchy as on step 3 (IntelliJ shows correctly the call hierarchy)
The text was updated successfully, but these errors were encountered: