All notable changes to the "vscode-java-debugger" extension will be documented in this file.
The format is based on Keep a Changelog and this project adheres to Semantic Versioning.
- Use code lens to run java program in a much simpler way. #375.
- Make args/vmArgs accept an array. #389.
- Make mainClass accept variables. #85.
- Fix: Still include test classes in classpaths when auto resolve maven project. #378.
- Fix: Duplicate class path during launching. #370.
- Fix: Update Active Editor oct icon to file instead of clock. #403.
- Fix: Launching the debuggee with the same JDK as java language server instead of JRE. #366.
- Fix: Avoid pop up error window many times for logpoints in a loop. #360.
- Fix: Debug buttons disabled. #411
- Fix: StepResponse/ContinueResponse should be sent before StoppedEvent. java-debug#134
- Fix: Runtime scope class path entries are missing. #402.
- Fix:
env
config in launch.json not respected. #393.
- Start without debugging. See #351.
- Add the validation to mainClass and projectName before launching. See #355.
- Add "Learn More" link jumps to the associated troubleshooting paragraph #360.
- Put recently used main class in the top #350.
- Enable evaluation for hovers #297.
- Distinguish user errors and system errors #288.
- Fix: vulnerabilities issue PR#356.
- Fix: NPE for CompletionsProvider PR#206.
- Fix: Debugger slow when watching variables #305.
- Fix: Should not include test classes in classpath #111.
- Add a troubleshooting page for common errors. See the troubleshooting guide.
- Build and publish the Java Debug Server plugin as p2 artifacts. See PR#191, PR#192.
- Auto select Java Debugger for .java file. See PR#329.
- Improve the launch.json auto-generation UX. See PR#342.
- Improve the logger coverage for the error response. See PR#190.
- Fix the attach error in JDK 10. See PR#187.
- Fix the Java Debug Server plugin build error in JDK 10. See PR#194.
- Add support for Logpoint. The minimum compatible VS Code version is 1.22. See the feature request #272
- Contribution from LunarArcanus: Fix the grammar issue in README. See PR#306.
- Fix the project's build errors in JDK 9/10. See PR#178
- Support auto-complete feature in debug console view. See the feature request #237
- Fix the ObjectCollectedException when enabling ExceptionBreakpoint. See Issue #182
- Fix the issue #277 that the debugger doesn't stop on caught/uncaught exceptions. See PR #172
- Fix the issue #273 that Chinese characters directory will cause messy code during stack trace's source looking up. See PR #170
- Support restart frame. See PR#160
- Enable hot code replace by default. See PR#263
- Wait for building successfully before launch debug session. See PR#257
- Automatically detect projectName when only one main class or project available. See PR#164
- Support conditional breakpoints. See PR#153, PR#154, PR#156
- Support prompting user for program arguments. See PR#245
- Fix the unsupported breakpoint at method entry/exit issue. See PR#129
- Fix the issue when the projectName is not specified, the expression evaluation doesn't work. See PR#156
- Fix VMDisconnectionException in HCR. See PR#150
- Support hot code replace. See PR#225
- Support step filters when stepping. See PR#155
- Support expression evaluation. See PR#126, PR#131
- Publish the binaries to the maven central repository. See PR#132
- Adopt new VSCode 1.19.0 debug activation events. See PR#196
- Looking up the stack frame's associated source file from source containers to improve searching perf. See PR#127
- Add
stopOnEntry
andconsole
options for launch.json. See PR#177 - Support console input by launching the program in the integrated/external terminal. See PR#122
- Add debugging settings:
java.debug.settings.showHex
,java.debug.settings.showStaticVariables
,java.debug.settings.showQualifiedNames
,java.debug.settings.maxStringLength
. See README for details - Support project scope when resolving multiple-root project. See PR#174
- Fix single file build issue. See Issue#167
- Fix perf issue when debugging with "stopOnEntry". See PR#115
- Fix the unable to start debugging issueIssue#146
- Support debugging java 9 project. See Issue#47
- Support debugging standalone java file. See Issue#94
- Support "cwd" and "env" in launch.json. See Issue#12, Issue#75
- Build workspace before starting debugger. See Issue#32
- Show progress when initializing the launch.json. See PR#106
- Get debug settings from VSCode user preferences. See PR#135,PR#94
- Fix perf issue on getting locations of breakpoint. See Issue#49
- Show warning message when the debugger and the debuggee run in the different versions of JVMs. See Issue#30
- Automatically resolve the main class during launching. See Issue#9
- Fully support external source files together with the changes from VSCode. See PR#58
- Adopt the new DebugConfigurationProvider protocol of VS Code. See PR#87
- Display the function names in the format of ClassName.MethodName(Parameter List...).. See PR#73
- Improve the call stack display info for the files without sources. See PR#72
- Fix the inconsistent URI issue when set breakpoint request. See PR#84
- Avoid two stopped events for step and breakpoint. See Issue#14
- Fix the issue that JDT search might return multiple results from the same project. See Issue#21
- Avoid send error messages after debugger adapter stopped. See PR#75
- Fix several exception cases. See PR#64, PR#67, PR#74
- Launch/Attach
- Breakpoints
- Exceptions
- Pause & Continue
- Step In/Out/Over
- Variables
- Callstacks
- Threads
- Debug console