Make the setting 'java.import.gradle.java.home' to be machine-overridable #2624
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Jinbo Wang jinbwan@microsoft.com
We have an enterprise partner that is trying to adopt VS Code as their Java development tool. To help their team to on board to VS Code more smoothly, they developed an internal command line tool to generate Java settings in .vscode/settings.json by one-click. They hope all JDK related settings to be workspace changable. This is a reasonable idea since workspace-level settings are more easily customized by third-party tools.
In addition, we already do that for most JDK-related settings such as 'java.jdt.ls.java.home', 'java.configuration.runtimes', it makes sense for me to change
java.import.gradle.java.home
to machine-overridable.