Get the latest Apache NetBeans VSCode extension from the official VS Code market place (The Red Hat extension requires JDK 11 or above.) VS Code already has support for Java, provided by an extension created by Red Hat, though what that extension misses are the following features that VSNetBeans provides out of the box: By using VSNetBeans, you're using the same Java tools that are part of Apache NetBeans, so that we hope that VSNetBeans will provide a new avenue for feedback to the Apache NetBeans project. And, if not, that's also fine.įull Java editing and debugging support is provided by VSNetBeans directly in your VSCode environment. Install VSNetBeans into VS Code, use it, and maybe you'll want to try the complete Apache NetBeans experience, which is Apache NetBeans.
Then start the debug and watch out for the generated commands and you can find what is wrong by analyzing the commands used to launch the application.īelow is an example of a config item in `launch.VSNetBeans, the Apache NetBeans Extension for Visual Studio Code, is created as a promotional tool by the Apache NetBeans community for VS Code users. To ensure you are using the correct config, first, find out the command line details using java.exe which is required to run your application, and then configure this command using the launch.json file.Īlso, configure the console of the debug session to be the integrated terminal and lunch the debug with or without the `launch.json' file.
I tried to set the classpath to point to the generated *.class` binary files but it didn't work I think because I need to specify each and everyone which wasn't possible. You must build the project using mvn install to generate the required jar files for the project which are defined in pom.xml' for all modules. You need to define a lunch request in the launch.json file and set the classpath to point to the correct jar files. It seems that the classpath is not set automatically or not set correctly when you try t debug without using a launch config. In my case, I get the same error when I am debugging a multi-module maven project.
0 kommentar(er)
