Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VSCode not displaying intellisense for team created library jar #522

Open
Crossle86 opened this issue Jan 18, 2022 · 2 comments
Open

VSCode not displaying intellisense for team created library jar #522

Crossle86 opened this issue Jan 18, 2022 · 2 comments

Comments

@Crossle86
Copy link

We have our own utility library developed on the same PC that hosts both that library and the robot code in VSC. The library jar is deployed to the local maven cache and we have a vendordep in the VSC project that includes that library jar into the robot project. The library code jar is found and loaded and we can successfully use the library in robot code. However, the library sources jar deployed with the code jar is not found by VSC, so there is no intellisense or ability to open a method declaration and see the source, like you can with the other libraries included via vendordeps.

Haven't had any luck solving this on my own...

@ThadHouse
Copy link
Member

That's all normally handled by gradle, we don't touch that process at all. Have you tried resetting the vscode Intellisense engine? In the command Palette run clean Java Workspace (or something like that, I can never remember the exact name). Past that, can you post a screenshot of the maven folder with the artifacts? It's very specific how it wants to find the sources and javadoc jars.

@Crossle86
Copy link
Author

I tried gradle clean command which helps at times but not with this. A side note, clean used to run without errors. This week a gradle clean (executed from VSCode WPILib command list) results in an error, complaining about not being able to delete the build director in the project. Today, when the happened, build directory was gone. Last time I did this, the build directory was present but inaccessible.

Back to the intellisense problem, here is screen shot of maven cache and the vendordep used to access the library.
Maven Cache
robotlib.json.txt
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants