-
Notifications
You must be signed in to change notification settings - Fork 408
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
Expose Java Classpath #48
Comments
* New debug adapter Signed-off-by: Jinbo Wang <jinbwan@microsoft.com> * refactor debug adapter * Remove non-unicode chars in code * Display error code in user message * Refactor AdapterUtils * fix review comments * Remove the unnecessary cwd option from launch arguments * Refactor the utility method name * fix setVariable and evaluate error message * Add explict id for ErrorCode enum class
We probably need to expose classpath per scope, i.e. compile vs test for Maven, but also runtime/provided. For Gradle projects, scope is a more "open" notion, not only are the scopes named differently (compile, compileTest) but it's open to customization. We need a way to extract those informations from Buildship's APIs, ideally. @oehme, @donat any pointers? |
Note: with Java 9's modulepath, we have an extra level of project dependencies |
@fbricon Actually, we're in the process of adding support separating scopes in the Eclipse runtime classpath. See the related issue and my feature branch. Basically, the idea is that the Gradle Here's an example
The scope information is based on the source set names ( |
Exposing Java classpath for the current workspace to the Java Script side can be very useful for other extensions. (https://code.visualstudio.com/docs/extensionAPI/vscode-api#_extensions)
The text was updated successfully, but these errors were encountered: