-
Notifications
You must be signed in to change notification settings - Fork 39
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
Send command across different workspace folders #24
Comments
I think it's something that can be implemented by jdt.ls, coc-java can't help since it doesn't parse your code. |
@chemzqm thank you for your answers! It sounds to me as well that this should be handled by jdt.ls. But I think this is a decision they made to keep the jar file and the source code independent. ie: they want to show the jar content rather than the source, as the source can be modified without the jar being recompiled. So they prefer showing the jar content rather than the source to avoid inconsistency. At least, this is my understanding.. |
The language server need to provide such kind of feature, let me know if jdt.ls could. |
Isn't this the
At least with Eclipse (the IDE, not the LS), |
From [email protected], there is shared index support. Try configurations |
Hello there,
Thanks for your awesome work. coc-java works great!
I am wondering if it is possible to specify another workspace when issuing a command with Coc plugin? Or is there anyway of changing temporarily the workspace folder in use?
The workflow I try to do is:
Given that workspaceA and workspaceB are loaded as workspace folders. From workspaceA, I want to goto the definition of a class Foo, but its definition is only available inside workspaceB. I would like to issue the command temporarily on workspaceB instead of workspaceA from a file contained in workspaceA.
Why?
jdtls tries to decompile the jar instead of jumping to the code. Even if I configure the thing properly via eclipse, I can see the code of Foo, but it does not point at the source file in workspaceB (it generates a new source file). Which I find annoying, I want to jump inside the other workspace instead.
The text was updated successfully, but these errors were encountered: