Thanks for your interest in Java on Visual Studio Code! This FAQ will hopefully answer some of the questions you may have.
Yes. All the Java Extensions provided by Red Hat, Microsoft, and Pivotal are open source, as well as most extensions supported by the community. You can find their corresponding repositories on GitHub from the Marketplace pages.
Definitely. We use GitHub issues to track incoming requests and planned work for each of our extensions. Currently we're working on adding more refactoring and linting features to enhance the editing productivity, as well as some performance improvements to make it even faster.
Most of our work is collected from and prioritized by customer feedback. If you're interested in providing your thoughts, you can either go directly to our project repositories to submit a new issue or use this Survey Link to share your thoughts.
We do have limited capacity within the team and we'd really like to encourage more contributions from the great Java community. If you're passionate about your idea and would like to help fellow Java developers, you're welcome to join us! Some areas worth considering including Gradle support, code analysis and test coverage tools, profiler, and additional framework support including DropWizard, JavaFX, JPA, Play, Akka, OSGi.
Sure. Keymap extensions in VS Code modify the VS Code shortcuts to match those of other editors. You can find IntelliJ IDEA Keybindings, Eclipse Keymap as well as keymaps for other popular editors in Keymaps category of extensions in the Marketplace.
You may Sign up to follow the latest of Java on Visual Studio Code.
We're currently publishing our updates at The Visual Studio Blog, which will report all our major features and improvements.
While you're using Java within VS Code, you might also see a Release Notes once you update the Java Extension Pack. That will give you an overview on the notable updates included in the extensions.
Thanks to the upstream update from JDT, you can now build your project up to Java 14 with VS Code as well. To use the experimental/preview language features, you need to modify your project settings.
Maven - modify pom.xml:
<build>
<pluginManagement>
<plugins>
<plugin>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<release>14</release>
<compilerArgs>--enable-preview</compilerArgs>
</configuration>
</plugin>
</plugins>
</pluginManagement>
</build>Gradle:
sourceCompatibility = 14
tasks.withType(JavaCompile) {
options.compilerArgs += '--enable-preview'
}
tasks.withType(Test) {
jvmArgs += "--enable-preview"
}Note: If you are modifying a project that was already opened in VS Code, you may need to force clean the workspace and reload. To do so, run command Java: Clean the Java language server workspace.
When using the Java extension behind a corporate proxy, you might need to let the Java Language server know how to connect to the Internet, in order to download build runtimes, Java dependencies, and their sources through that proxy.
This is done by configuring the java.jdt.ls.vmargs setting in VS Code preferences (all on one line):
{
"java.jdt.ls.vmargs": "-Dhttp.proxyHost=webproxy.corp.net -Dhttp.proxyPort=proxyport -Dhttp.proxyUser=user -Dhttp.proxyPassword=password -Dhttps.proxyHost=webproxy.corp.net -Dhttps.proxyPort=proxyport -Dhttps.proxyUser=user -Dhttps.proxyPassword=password"
}Currently we don't plan to extend the Java support to Visual Studio. There are already great IDEs for Java and we're focusing on VS Code to provide a lightweight experience in a polyglot editor.
Currently we support Chinese in addition to English for a few extensions including Debugger for Java, Java Test Runner, Maven for Java, Java Dependency Viewer. To learn how to switch the VS Code display language, see Display Languages.
You can contribute to the extension repositories if you're interested in additional display language support.
You can visit the Java for Visual Studio Code wiki to find answers regarding: