Visual Java

Jvider - Visual Interface Designer for JAVA Swing. Jvider Features. Standard Java™ Swing components; GridBagLayout is used for layout (no absolute positioning). In this document you will use the Visual Debugger to explore the Anagram Game sample project, which is a Java Swing application distributed with NetBeans. This document will demonstrate how to take a GUI snapshot of the application and then work with the snapshot to locate source code, add listeners to events, and view the event log of GUI.

Visual Java Programming

This tutorial shows you how to write and run Hello World program in Java with Visual Studio Code. It also covers a few advanced features, which you can explore by reading other documents in this section.

For an overview of the features available for Java in VS Code, see Java Language Overview

If you run into any issues when following this tutorial, you can contact us by clicking the Report an issue button below.

Setting up VS Code for Java development

Coding Pack for Java

To help you set up quickly, you can install the Coding Pack for Java, which includes VS Code, the Java Development Kit (JDK), and essential Java extensions. The Coding Pack can be used as a clean installation, or to update or repair an existing development environment.

Install the Coding Pack for Java - macOS

Note: The Coding Pack for Java is only available for Windows and macOS. For other operating systems, you will need to manually install a JDK, VS Code, and Java extensions.

Installing extensions

If you are an existing VS Code user, you can also add Java support by installing Java Extension Pack, which includes these extensions:

The Java Extension Pack provides a Quick Start guide and tips for code editing and debugging. It also has a FAQ that answers some frequently asked questions. Use the command Java: Getting Started from the Command Palette (⇧⌘P (Windows, Linux Ctrl+Shift+P)) to launch the guide.

You can also install extensions separately. The Extension Guide is provided to help you. You can launch the guide with the Java: Extension Guide command.

For this tutorial, the only required extensions are:

Settings for the JDK

Supported Java versions

The supported version for running the VS Code for Java extension and the supported version for your projects are two separate runtimes. To run VS Code for Java, Java SE 11 or above version is required; for projects, VS Code for Java supports projects with version 1.5 or above. For more details, refer to Configure JDK.

Using Java runtime configuration wizard

To help you configure correctly, we provide a runtime configuration wizard. You can launch the wizard by opening the Command Palette (⇧⌘P (Windows, Linux Ctrl+Shift+P)) and typing the command Java: Configure Java Runtime, which will display the configuration user interface below.

Note: To configure multiple JDKs, see Configure JDK. To enable Java preview features, see How can I use VS Code with new Java versions

Using VS Code settings

Alternatively, you can configure JDK settings using the VS Code Settings editor. A common way to do this is setting the value of the JAVA_HOME system environment variable to the install location of the JDK, for example, C:Program FilesJavajdk-13.0.2. Or if you want to configure only VS Code to use the JDK, use the java.home setting in VS Code's User or Workspace settings.

Installing a Java Development Kit (JDK)

When you need install a JDK, we recommend you to consider installing from one of these sources:

Creating a source code file

Create a folder for your Java program and open the folder with VS Code. Then in VS Code, create a new file and save it with the name When you open that file, the Java Language Server automatically starts loading, and you should see a loading icon on the right side of the Status Bar. After it finishes loading, you will see a thumbs-up icon.

Note: If you open a Java file in VS Code without opening its folder, the Java Language Server might not work properly.

VS Code will also try to figure out the correct package for the new type and fill the new file from a template. See Create new file.

You can also create a Java project using the Java: Create Java Project command. Bring up the Command Palette (⇧⌘P (Windows, Linux Ctrl+Shift+P)) and then type java to search for this command. After selecting the command, you will be prompted for the location and name of the project. You can also choose your build tool from this command.

Visual Studio Code also supports more complex Java projects, see Project Management.

Editing source code

You can use code snippets to scaffold your classes and methods. VS Code also provides IntelliSense for code completion, and various refactor methods.

To learn more about editing Java, see Java Editing.

Running and debugging your program

To run and debug Java code, set a breakpoint, then either press F5 on your keyboard or use the Run > Start Debugging menu item. You can also use the Run Debug CodeLens options in the editor. After the code compiles, you can see all your variables and threads in the Run view.

The debugger also supports advanced features such as Hot Code replacement and conditional breakpoints.

For more information, see Java Debugging.

More features

The editor also has much more capability for your Java workload.

  • Editing Java explains how to navigate and edit Java in more details
  • Debugging illustrates all the key features of the Java Debugger
  • Testing provides comprehensive support for JUnit and TestNG framework
  • Java Project Management shows you how to use a project view and work with Maven
  • Spring Boot and Tomcat and Jetty demonstrate great framework support
  • Java Web Apps shows how to work with Java Web App in VS Code

Provides Java ™ language support viaEclipse ™ JDT Language Server, which utilizesEclipse ™ JDT, M2Eclipse and Buildship.

  1. Install the Extension
  2. If you do not have a Java Development Kit correctly set
    • Download and install a recent Java Development Kit (latest Java 11 is the current minimum requirement).
  3. Extension is activated when you first access a Java file
    • Recognizes projects with Maven or Gradle build files in the directory hierarchy.
  • Supports code from Java 1.5 to Java 16
  • Maven pom.xml project support
  • Basic Gradle Java project support (Android not supported)
  • Standalone Java files support
  • As-you-type reporting of parsing and compilation errors
  • Code completion
  • Code/Source actions / Refactoring
  • Javadoc hovers
  • Organize imports
    • triggered manually or on save
    • when pasting code into a java file with Ctrl+Shift+v (Cmd+Shift+v on Mac).
  • Type search
  • Code outline
  • Code folding
  • Code navigation
  • Code lens (references/implementations)
  • Highlights
  • Code formatting (on-type/selection/file)
  • Code snippets
  • Annotation processing support (automatic for Maven projects)
  • Semantic selection
  • Diagnostic tags
  • Call Hierarchy
  • Type Hierarchy

Please note that Gradle-based Android projects are not supported.

To launch and debug your Java programs, it's recommended you install Java Debug Extension for Visual Studio Code.

See the changelog for the latest release. You might also find useful information in the project Wiki.

Java Tooling JDK

This JDK will be used to launch the Java Language Server. And by default, will also be used to compile your projects.

The path to the Java Development Kit can be specified by the java.home setting in VS Code settings (workspace/user settings). If not specified, it is searched in the following order until a JDK meets current minimum requirement.

  • the JDK_HOME environment variable
  • the JAVA_HOME environment variable
  • on the current system path

Project JDKs

If you need to compile your projects against a different JDK version, it's recommended you configure the java.configuration.runtimes property in your user settings, eg:

The default runtime will be used when you open standalone Java files.

The following commands are available:

  • Switch to Standard Mode: switches the Java Language Server to Standard mode. This command is only available when the Java Language Server is in LightWeight mode.
  • Java: Update Project (Shift+Alt+U): is available when the editor is focused on a Maven pom.xml or a Gradle file. It forces project configuration / classpath updates (eg. dependency changes or Java compilation level), according to the project build descriptor.
  • Java: Import Java Projects into Workspace: detects and imports all the Java projects into the Java Language Server workspace.
  • Java: Open Java Language Server Log File: opens the Java Language Server log file, useful for troubleshooting problems.
  • Java: Open Java Extension Log File: opens the Java extension log file, useful for troubleshooting problems.
  • Java: Open All Log Files: opens both the Java Language Server log file and the Java extension log file.
  • Java: Force Java Compilation (Shift+Alt+B): manually triggers compilation of the workspace.
  • Java: Open Java Formatter Settings: opens the Eclipse formatter settings. Creates a new settings file if none exists.
  • Java: Clean Java Language Server Workspace: cleans the Java language server workspace.
  • Java: Attach Source: attaches a jar/zip source to the currently opened binary class file. This command is only available in the editor context menu.
  • Java: Add Folder to Java Source Path: adds the selected folder to its project source path. This command is only available in the file explorer context menu and only works for unmanaged folders.
  • Java: Remove Folder from Java Source Path: removes the selected folder from its project source path. This command is only available in the file explorer context menu and only works for unmanaged folders.
  • Java: List All Java Source Paths: lists all the Java source paths recognized by the Java Language Server workspace.
  • Java: Show Build Job Status: shows the Java Language Server job status in Visual Studio Code terminal.
  • Java: Go to Super Implementation: goes to the super implementation for the current selected symbol in editor.

The following settings are supported:

  • java.home : Absolute path to JDK home folder used to launch the Java Language Server. Requires VS Code restart.

  • : Extra VM arguments used to launch the Java Language Server. Requires VS Code restart.

  • java.errors.incompleteClasspath.severity : Specifies the severity of the message when the classpath is incomplete for a Java file. Supported values are ignore, info, warning, error.

  • java.trace.server : Traces the communication between VS Code and the Java language server.

  • java.configuration.updateBuildConfiguration : Specifies how modifications on build files update the Java classpath/configuration. Supported values are disabled (nothing happens), interactive (asks about updating on every modification), automatic (updating is automatically triggered).

  • java.configuration.maven.userSettings : Path to Maven's user settings.xml.

  • java.configuration.checkProjectSettingsExclusions: Controls whether to exclude extension-generated project settings files (.project, .classpath, .factorypath, .settings/) from the file explorer. Defaults to true.

  • java.referencesCodeLens.enabled : Enable/disable the references code lenses.

  • java.implementationsCodeLens.enabled : Enable/disable the implementations code lenses.

  • java.signatureHelp.enabled : Enable/disable signature help support (triggered on ().

  • java.contentProvider.preferred : Preferred content provider (see 3rd party decompilers available in vscode-java-decompiler).

  • java.import.exclusions : Exclude folders from import via glob patterns. Use ! to negate patterns to allow subfolders imports. You have to include a parent directory. The order is important.

  • java.import.gradle.enabled : Enable/disable the Gradle importer.

  • Specify the Gradle distribution used by the Java extension:

    • java.import.gradle.wrapper.enabled: Use Gradle from the '' file. Defaults to true.
    • java.import.gradle.version: Use Gradle from the specific version if the Gradle wrapper is missing or disabled.
    • java.import.gradle.home: Use Gradle from the specified local installation directory or GRADLE_HOME if the Gradle wrapper is missing or disabled and no 'java.import.gradle.version' is specified.
  • java.import.gradle.arguments: Arguments to pass to Gradle.

  • java.import.gradle.jvmArguments: JVM arguments to pass to Gradle.

  • java.import.gradle.user.home: setting for GRADLE_USER_HOME.

  • java.import.gradle.offline.enabled: Enable/disable the Gradle offline mode. Defaults to false.

  • java.import.maven.enabled : Enable/disable the Maven importer.

  • java.autobuild.enabled : Enable/disable the 'auto build'.

  • java.maxConcurrentBuilds: Set max simultaneous project builds.

  • java.completion.enabled : Enable/disable code completion support.

  • java.completion.overwrite : When set to true, code completion overwrites the current text. When set to false, code is simply added instead.

  • java.completion.guessMethodArguments : When set to true, method arguments are guessed when a method is selected from as list of code assist proposals.

  • java.completion.filteredTypes: Defines the type filters. All types whose fully qualified name matches the selected filter strings will be ignored in content assist or quick fix proposals and when organizing imports. For example 'java.awt.*' will hide all types from the awt packages.

  • java.completion.favoriteStaticMembers : Defines a list of static members or types with static members.

  • java.completion.importOrder : Defines the sorting order of import statements.

  • java.progressReports.enabled : [Experimental] Enable/disable progress reports from background processes on the server.

  • java.format.enabled : Enable/disable the default Java formatter.

  • java.format.settings.url : Specifies the url or file path to the Eclipse formatter xml settings.

  • java.format.settings.profile : Optional formatter profile name from the Eclipse formatter settings.

  • java.format.comments.enabled : Includes the comments during code formatting.

  • java.format.onType.enabled : Enable/disable on-type formatting (triggered on ;, } or <return>).

  • java.foldingRange.enabled: Enable/disable smart folding range support. If disabled, it will use the default indentation-based folding range provided by VS Code.

  • java.maven.downloadSources: Enable/disable download of Maven source artifacts as part of importing Maven projects.

  • java.maven.updateSnapshots: Force update of Snapshots/Releases. Defaults to false.

  • java.codeGeneration.hashCodeEquals.useInstanceof: Use 'instanceof' to compare types when generating the hashCode and equals methods. Defaults to false.

  • java.codeGeneration.hashCodeEquals.useJava7Objects: Use Objects.hash and Objects.equals when generating the hashCode and equals methods. This setting only applies to Java 7 and higher. Defaults to false.

  • java.codeGeneration.useBlocks: Use blocks in 'if' statements when generating the methods. Defaults to false.

  • java.codeGeneration.generateComments: Generate method comments when generating the methods. Defaults to false.

  • java.codeGeneration.toString.template: The template for generating the toString method. Defaults to ${object.className} [${}=${member.value}, ${otherMembers}].

  • java.codeGeneration.toString.codeStyle: The code style for generating the toString method. Defaults to STRING_CONCATENATION.

  • java.codeGeneration.toString.skipNullValues: Skip null values when generating the toString method. Defaults to false.

  • java.codeGeneration.toString.listArrayContents: List contents of arrays instead of using native toString(). Defaults to true.

  • java.codeGeneration.toString.limitElements: Limit number of items in arrays/collections/maps to list, if 0 then list all. Defaults to 0.

  • java.selectionRange.enabled: Enable/disable Smart Selection support for Java. Disabling this option will not affect the VS Code built-in word-based and bracket-based smart selection.

  • java.showBuildStatusOnStart.enabled: Automatically show build status on startup. Defaults to false.

  • java.project.outputPath: A relative path to the workspace where stores the compiled output. Only effective in the WORKSPACE scope. The setting will NOT affect Maven or Gradle project.

  • java.project.referencedLibraries: Configure glob patterns for referencing local libraries to a Java project.

  • java.completion.maxResults: Maximum number of completion results (not including snippets). 0 (the default value) disables the limit, all results are returned. In case of performance problems, consider setting a sensible limit.

  • java.configuration.runtimes: Map Java Execution Environments to local JDKs.

  • java.server.launchMode:

    • Standard: Provides full features such as intellisense, refactoring, building, Maven/Gradle support etc..
    • LightWeight: Starts a syntax server with lower start-up cost. Only provides syntax features such as outline, navigation, javadoc, syntax errors. The lightweight mode won't load thirdparty extensions, such as java test runner, java debugger, etc.
    • Hybrid: Provides full features with better responsiveness. It starts a standard language server and a secondary syntax server. The syntax server provides syntax features until the standard server is ready. And the syntax server will be shutdown automatically after the standard server is fully ready.

    Default launch mode is Hybrid. Legacy mode is Standard

  • java.sources.organizeImports.starThreshold: Specifies the number of imports added before a star-import declaration is used, default is 99.

  • java.sources.organizeImports.staticStarThreshold: Specifies the number of static imports added before a star-import declaration is used, default is 99.

  • java.semanticHighlighting.enabled: Enable/disable Semantic Highlighting for Java files. Defaults to true.

  • java.imports.gradle.wrapper.checksums: Defines allowed/disallowed SHA-256 checksums of Gradle Wrappers.

  • java.project.importOnFirstTimeStartup: Specifies whether to import the Java projects, when opening the folder in Hybrid mode for the first time. Supported values are disabled (never imports), interactive (asks to import or not), automatic (always imports). Default to interactive.

  • java.project.importHint: Enable/disable the server-mode switch information, when Java projects import is skipped on startup. Defaults to true.

  • Specifies the location to the JVM used to run the Gradle daemon. Visio studio.

  • java.project.resourceFilters: Excludes files and folders from being refreshed by the Java Language Server, which can improve the overall performance. For example, ['node_modules','.git'] will exclude all files and folders named 'node_modules' or '.git'. Defaults to ['node_modules','.git'].

  • java.templates.fileHeader: Specifies the file header comment for new Java file. Supports configuring multi-line comments with an array of strings, and using ${variable} to reference the predefined variables.

  • java.templates.typeComment: Specifies the type comment for new Java type. Supports configuring multi-line comments with an array of strings, and using ${variable} to reference the predefined variables.

  • java.references.includeAccessors: Include getter, setter and builder/constructor when finding references. Default to true.

  • java.configuration.maven.globalSettings : Path to Maven's global settings.xml.

  • java.eclipse.downloadSources : Enable/disable download of Maven source artifacts for Eclipse projects.

  • : Show the recommended Dependency Analytics extension.

  • java.references.includeDecompiledSources : Include the decompiled sources when finding references. Default to true.

  • java.project.sourcePaths: Relative paths to the workspace where stores the source files. Only effective in the WORKSPACE scope. The setting will NOT affect Maven or Gradle project.

  • java.typeHierarchy.lazyLoad: Enable/disable lazy loading the content in type hierarchy. Lazy loading could save a lot of loading time but every type should be expanded manually to load its content.

  • java.codeGeneration.insertionLocation: Specifies the insertion location of the code generated by source actions. Defaults to afterCursor.

    • afterCursor: Insert the generated code after the member where the cursor is located.
    • beforeCursor: Insert the generated code before the member where the cursor is located.
    • lastMember: Insert the generated code as the last member of the target type.
  • java.settings.url : Specifies the url or file path to the workspace Java settings. See Setting Global Preferences

  • java.symbols.includeSourceMethodDeclarations : Include method declarations from source files in symbol search. Defaults to false.

Semantic Highlighting is controlled by the java.semanticHighlighting.enabled preference. When enabled, it fixes numerous syntax highlighting issues with the default Java Textmate grammar. However, you might experience different small issues, particularly a delay when it kicks in, as it needs to be computed by the Java Language server, when opening a new file or when typing.

  1. Check the status of the language tools on the lower right corner (marked with A on image below).It should show ready (thumbs up) as on the image below. You can click on the status and open thelanguage tool logs for further information in case of a failure.
  1. Read the troubleshooting guide for collecting informations about issues you might encounter.

  2. Report any problems you face to the project.


This is an open source project open to anyone. Contributions are extremely welcome!

For information on getting started, refer to the CONTRIBUTING instructions.

Continuous Integration builds can be installed from Download the most recent java-<version>.vsix file and install it by following the instructions here.Stable releases are archived under

Also, you can contribute your own VSCode extension to enhance the existing features by following the instructions here.

  • File a bug in GitHub Issues,
  • Chat with us on Gitter,
  • Tweet us with other feedback.

Visual Javafx

EPL 2.0, See LICENSE for more information.