Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upDon't inject classpath into modulePaths config #649
Conversation
It is OK to leave modulePaths empty. What is not OK is to inject the classPaths into modulePaths.
|
Hey @hexiaokai, I see limitations in working with modules (Java 9+) on VS Code. First issue I found is that it is incorrectly injecting a classpath into the modulePaths property. |
|
@brunoborges could you provide a sample project to help reproduce this issue? i'm trying to understand the purpose of the fix... |
|
https://github.com/brunoborges/fx2048 is a Java project that uses Gradle to run, and so far it has been extremely painful to get VS Code to debug it. |
|
this project is using JavaFX 12, actually it needs to be launched as modules. Currently the debugger put the javafx libraries into
|
|
I'm not following... |
It is OK to leave modulePaths empty. What is not OK is to inject the classPaths into modulePaths.