Language Server Java 8+ ... launch configuration supports debugging and running Java applications using JDK8 or newer.
Run main | Debug main
code lense is selected in the code.Default launch configurations provided by Language Server can modified in launch.json
file using intellisense for available options.
Program arguments, VM options, evironment variables,... can be set in Run Configuration panel a part of Explorer. The panel is sufficient for all typical use-cases Java programmer faces. Only advanced, expert scenarios may require touching of launch.json
(which still takes precedence).
Class level refactorings as well as variable refactorings are supported in VSCode via Apache NetBeans extension. See following screenshots:
Some refactorings are two steps with like Override method ... where method to be overriden is selected in 2nd step:
Change method parameters refactoring is provided using dedidacated form allowing to change, add, move, remove method parameters.
Out of the box support for organizing imports in Java sources is available. It removes unused imports, groups imports by packages and updates your imports whenever a file is saved. In addition to the defaults, there is a rich set of configuration options.
Go to VSCode Preferences | Settings
and search for NetBeans to set Netbeans > Java > Imports:
options:
Count For Using Star Import
- Class count to use a star-import, 999 means any numberCount For Using Static Star Import
- Members count to use a static star-import, 999 means any numberGroups
- Groups of import statements (specified by their package prefixes) and their sorting order. Import statements within a group are ordered alphabeticallyAnd Netbeans > Java > On Save: Organize Imports
- Enable organize imports action on a document save
NetBeans Language Server provides Test Explorer view which allows to run all tests in a project, examine the results, go to source code and run particular test.
NetBeans Language Server allows Java like debugging of native images produced by GraalVM EE native-image tool. It is provided using GDB and via new Run configuration named Launch Native Image. This experimental feature works now only on Linux with certain version of GDB, see above. GraalVM Enterprise Edition is needed as it produces full debug information for native images, at this time.
In order to debug native image applications it is necessary to build such native image with debug information available. It can be done by providing following switches for native-image tool:
-g -O0
or-H:Debug=2 -H:Optimize=0
.It is possible to use Native-Image Maven Plugin to run native-image builds for Maven projects. In this case add following <buildArgs>
into plugin <configuration>
:
<buildArgs> <buildArg>-g</buildArg> <buildArg>-O0</buildArg> </buildArgs>
Setting project's Maven pom.xml to skip native-image build everytime when project is being built is a good practice.
When native image is built, including debug info then add Launch Native Image configuration to launch.json. Select it in Run & Debug activity window and press F5 to debug Java source code on native image.
The user projects are built, run and debugged using the same JDK which runs the Apache NetBeans Language Server. The JDK is being searched in following locations:
netbeans.jdkhome
setting (workspace then user settings)java.home
setting (workspace then user settings)JDK_HOME
environment variableJAVA_HOME
environment variableAs soon as one of the settings is changed, the Language Server is restarted.
It is possible to run Apache NetBeans Language Server per workspace (VSCode window). This allows separation of Language Server for given project as Language Server JVM is not shared for more VSCode open workspaces (projects). It is possible to change this in Preferences | Settings | Netbeans: Userdir
. Set to local
to use dedicated Language Server per workspace or set to global
(this is default) to have one Language Server for all VSCode workspaces.
Apache NetBeans Language Server extension isn't the only Java supporting extension. To avoid duplicated code completion and other misleading clashes the extension disables certain functionality known to cause problems, this is done per Workspace.
This behavior can be disabled by setting netbeans.conflict.check
setting to false
.
Read building instructions to help Apache community to improve the extension.