oracle / javavscode

Java platform support for Visual Studio Code for full featured Java development (edit-compile-debug & test cycle)
Apache License 2.0
231 stars 31 forks source link

fails to find dependency jar with certain naming #119

Closed robaho closed 6 months ago

robaho commented 9 months ago

Using the latest extension v1.0.1

We have a jar, solPackage-2.9.0.1.jar and it is not found, leading to missing class errors in the editor.

If I change the jar name to sol_package-2.9.0.1.jar it works.

The language server fails to recognize a jar in the /lib that is marked in Gradle as a dependency. All of the other jars in the directory appear. I detect this by looking at Projects > Configurations > Implementation > Local Files and the jar is not listed.

Gradle compiles and runs the project fine. The only issue is that the editor marks the classes as not found.

If I change to the netbeans extension, it finds and uses that jar fine, same with the redhat extension.

Is there a debug option I can enable to trace into why this is happening? I have to assume there is some sort of regex verification that is failing.

robaho commented 9 months ago

Curiously, sol-package-2.9.0.1.jar does not work either.

robaho commented 8 months ago

I have encountered this with another set of jars. the prometheus client jars are

simpleclient_common-0.16.0.jar simpleclient_hotspot-0.16.0.jar simpleclient_httpserver-0.16.0.jar simpleclient_pushgateway-0.16.0.jar

none of these jars will be added to the project dependencies. Other jars are added as expected.

Achal1607 commented 8 months ago

Okay will try to reproduce this

Achal1607 commented 6 months ago

Hey @robaho, I tried reproducing this but in my case prometheus client jars are rightly detected by the extension. So, can you once try to clean the cache of the extension for this workspace and then again try, maybe it can be some cache issue. For clearing cache pls refer to troubleshooting guide.

Achal1607 commented 6 months ago

Please feel free to reopen this issue, if you face this issue again. For now closing this issue due to inactivity.