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
Doesn't recognize imports in classpath on a simple project #93
Comments
Should be problem of your language server, checkout https://github.com/neoclide/coc.nvim/wiki/Debug-language-server#using-output-channel |
I'm sorry could you help me some more. I didn't find anything wrong with the output. That's my relevant part in the code: And this is the error part: It has a lot more lines but I don't think they are relevant, maybe this initial part here that has the errors too: |
Any help would be greately appreciated. I don't know my way around this stuff and couldn't find relevant information neither at the eclipse jdt page, or the vscode-java or anything |
Update: jdt will in fact not recognize your env classpath. |
@mdacach But it still raises the unresolve error. Did you have similar problems ever? Thanks! |
Same issue here for me. |
I can't get the libraries of Princeton algs4 into working even after adding the path to the "java.project.referencedLibraries": [
"/home/andre/.local/share/algs4/algs4.jar",
"/home/andre/.local/share/algs4/lift/lib/algs4.jar",
"/home/andre/.local/share/algs4/lift/lib/introcs.jar",
"/home/andre/.local/share/algs4/lift/lib/stdlib.jar",
] Did any of you were able to get it working? UPDATE: After migrating from vim to neovim it worked very well! The issue is that |
coc-java doesn't seem to recognize my $CLASSPATH variable.
https://algs4.cs.princeton.edu/code/
I followed these instructions to set my classpath.
If I do :echo $CLASSPATH inside vim I get everything correctly, if I compile anything from the classpath it also works as expectedly. But coc-java does not offer completion regarding the classpath files and throws errors at every import from it.
This is a simple one file, not using anything.
The text was updated successfully, but these errors were encountered: