修改JAVA DEBUG插件名称以及Readme

This commit is contained in:
xiayuqi 2024-11-06 16:06:59 +08:00
parent 215fb32fd5
commit 089075bdcc
2 changed files with 129 additions and 77 deletions

202
README.md
View File

@ -1,63 +1,10 @@
[中文](#中文描述)|[English](#englishdescription)
# 中文描述
## 概述
这是一个基于 [Java Debug Server](https://github.com/Microsoft/java-debug) 的轻量级 Java 调试器,扩展了 [Red Hat 的 Java 语言支持](https://open-vsx.org/?search=kylinideteam.java)插件的功能。它允许用户使用 IDE调试 Java 代码。以下是其功能列表:
1. 支持 Java 8 和 11。
2. 支持远程调试。
3. 支持断点、单步执行、查看变量等基本调试功能。
4. 支持查看类路径、类加载器、方法栈等信息。
5. 支持查看本地变量、局部变量、实例变量、静态变量等信息。
6. 支持查看方法参数、返回值
- 启动/附加
- 断点/条件断点/日志点
- 异常
- 暂停与继续
- 单步进入/退出/覆盖
- 变量
- 调用栈
- 线程
- 调试控制台
- 评估
- 热代码替换
## 要求
- JDK版本 1.8.0 或更高版本)
- IDE版本 1.19.0 或更高版本)
- [Java 语言支持插件(KylinIDE 团队)](https://open-vsx.org/?search=kylinideteam.java)
## 安装
打开IDE按下`F1`键或同时按下`Ctrl`和`Shift`键再按`P`键打开命令面板选择“安装插件程序”然后输入“kylinideteam.vscode-java-debug”。
或者按下“Ctrl + P”启动IDE Quick Open粘贴以下命令然后按回车键。
```bash
ext install kylinideteam.vscode-java-debug
``````
## 使用方法:
- 启动IDE
- 打开一个Java项目Maven/Gradle/Eclipse/单个Java文件
- 打开一个Java文件以激活扩展
- 按下`F5`键
如果您在设置项目时遇到困难,请查看[Language Support for Java](https://open-vsx.org/search=kylinideteam.java) 的文档。
## 许可证
此插件根据[MIT许可证]获得许可(https://gitee.com/openkylin/vscode-java-debug/blob/master/LICENSE.txt).
# Englishdescription
# Debugger for Java
Modified based on the version 0.46 of vscode-java-debug
# Java Debug(Support OpenJDK11)
- Fork of vscjava.vscode-java-debug, modified on the lower version to support OpenJDK 11
- Modified based on the version 0.46 of vscode-java-debug
- A lightweight Java Debugger. It depends on the [Java(Support OpenJDK11)](https://open-vsx.org/?search=kylinideteam.java)
## Overview
A lightweight Java Debugger based on [Java Debug Server](https://github.com/Microsoft/java-debug) which extends the [Language Support for Java by Red Hat](https://open-vsx.org/?search=kylinideteam.java). It allows users to debug Java code using IDE. Here's a list of features:
Features:
- Launch/Attach
- Breakpoints/Conditional Breakpoints/Logpoints
- Exceptions
@ -71,28 +18,133 @@ A lightweight Java Debugger based on [Java Debug Server](https://github.com/Micr
- Hot Code Replace
## Requirements
- JDK (version 1.8.0 or later)
- IDE (version 1.19.0 or later)
- [Language Support for Java](https://open-vsx.org/?search=kylinideteam.java)
## Install
Open IDE and press `F1` or `Ctrl + Shift + P` to open command palette, select **Install Extension** and type `kylinideteam.vscode-java-debug`.
Or launch IDE Quick Open (`Ctrl + P`), paste the following command, and press enter.
```bash
ext install kylinideteam.vscode-java-debug
```
- JDK (version 1.8.0 or later), but Java(Support OpenJDK11) needs JDK11 or later, so JDK11 or later
- VSCode API (version 1.19.0 or later)
- [Java(Support OpenJDK11)](https://open-vsx.org/?search=kylinideteam.java)
## Use
- Launch IDE
- Launch VSCode or kylin-ide, or something like VSCode
- Open a Java project (Maven/Gradle/Eclipse/Single Java file)
- Open a Java file to activate the extensions
- Press `F5`
Please also check the documentation of [Language Support for Java](https://open-vsx.org/?search=kylinideteam.java) if you have trouble setting up your project.
## Options
- launch.json options description
- type: java
- request: launch or attach
## License
This extension is licensed under [MIT License](https://gitee.com/openkylin/vscode-java-debug/blob/master/LICENSE.txt).
### Launch
- `mainClass` - The fully qualified name of the class containing the main method. If not specified, the debugger automatically resolves the possible main class from current project.
- `${file}` - Current Java file.
- `com.mypackage.Main` - The fully qualified class name.
- `com.java9.mymodule/com.mypackage.Main` - The fully qualified module name and class name.
- `/path/to/Main.java` - The file path of the main class.
- `args` - The command line arguments passed to the program.
- `"${command:SpecifyProgramArgs}"` - Prompt user for program arguments.
- A space-separated string or an array of string.
- `sourcePaths` - The extra source directories of the program. The debugger looks for source code from project settings by default. This option allows the debugger to look for source code in extra directories.
- `modulePaths` - The modulepaths for launching the JVM. If not specified, the debugger will automatically resolve from current project. If multiple values are specified, the debugger will merge them together.
- `$Auto` - Automatically resolve the modulepaths of current project.
- `$Runtime` - The modulepaths within 'runtime' scope of current project.
- `$Test` - The modulepaths within 'test' scope of current project.
- `!/path/to/exclude` - Exclude the specified path from modulepaths.
- `/path/to/append` - Append the specified path to the modulepaths.
- `classPaths` - The classpaths for launching the JVM. If not specified, the debugger will automatically resolve from current project. If multiple values are specified, the debugger will merge them together.
- `$Auto` - Automatically resolve the classpaths of current project.
- `$Runtime` - The classpaths within 'runtime' scope of current project.
- `$Test` - The classpaths within 'test' scope of current project.
- `!/path/to/exclude` - Exclude the specified path from classpaths.
- `/path/to/append` - Append the specified path to the classpaths.
- `encoding` - The `file.encoding` setting for the JVM. Possible values can be found in https://docs.oracle.com/javase/8/docs/technotes/guides/intl/encoding.doc.html.
- `vmArgs` - The extra options and system properties for the JVM (e.g. -Xms\<size\> -Xmx\<size\> -D\<name\>=\<value\>), it accepts a string or an array of string.
- `projectName` - The preferred project in which the debugger searches for classes. There could be duplicated class names in different projects. This setting also works when the debugger looks for the specified main class when launching a program. It is required when the workspace has multiple java projects, otherwise the expression evaluation and conditional breakpoint may not work.
- `cwd` - The working directory of the program. Defaults to `${workspaceFolder}`.
- `env` - The extra environment variables for the program.
- `envFile` - Absolute path to a file containing environment variable definitions.
- `stopOnEntry` - Automatically pause the program after launching.
- `console` - The specified console to launch the program. If not specified, use the console specified by the `java.debug.settings.console` user setting.
- `internalConsole` - IDE debug console (input stream not supported).
- `integratedTerminal` - IDE integrated terminal.
- `externalTerminal` - External terminal that can be configured in user settings.
- `shortenCommandLine` - When the project has long classpath or big VM arguments, the command line to launch the program may exceed the maximum command line string limitation allowed by the OS. This configuration item provides multiple approaches to shorten the command line. Defaults to `auto`.
- `none` - Launch the program with the standard command line 'java [options] classname [args]'.
- `jarmanifest` - Generate the classpath parameters to a temporary classpath.jar file, and launch the program with the command line 'java -cp classpath.jar classname [args]'.
- `argfile` - Generate the classpath parameters to a temporary argument file, and launch the program with the command line 'java @argfile [args]'. This value only applies to Java 9 and higher.
- `auto` - Automatically detect the command line length and determine whether to shorten the command line via an appropriate approach.
- `stepFilters` - Skip specified classes or methods when stepping.
- `classNameFilters` - [**Deprecated** - replaced by `skipClasses`] Skip the specified classes when stepping. Class names should be fully qualified. Wildcard is supported.
- `skipClasses` - Skip the specified classes when stepping.
- `$JDK` - Skip the JDK classes from the default system bootstrap classpath, such as rt.jar, jrt-fs.jar.
- `$Libraries` - Skip the classes from application libraries, such as Maven, Gradle dependencies.
- `java.*` - Skip the specified classes. Wildcard is supported.
- `java.lang.ClassLoader` - Skip the classloaders.
- `skipSynthetics` - Skip synthetic methods when stepping.
- `skipStaticInitializers` - Skip static initializer methods when stepping.
- `skipConstructors` - Skip constructor methods when stepping.
### Attach
- `hostName` (required, unless using `processId`) - The host name or IP address of remote debuggee.
- `port` (required, unless using `processId`) - The debug port of remote debuggee.
- `processId` - Use process picker to select a process to attach, or Process ID as integer.
- `${command:PickJavaProcess}` - Use process picker to select a process to attach.
- an integer pid - Attach to the specified local process.
- `timeout` - Timeout value before reconnecting, in milliseconds (default to 30000ms).
- `sourcePaths` - The extra source directories of the program. The debugger looks for source code from project settings by default. This option allows the debugger to look for source code in extra directories.
- `projectName` - The preferred project in which the debugger searches for classes. There could be duplicated class names in different projects. It is required when the workspace has multiple java projects, otherwise the expression evaluation and conditional breakpoint may not work.
- `stepFilters` - Skip specified classes or methods when stepping.
- `classNameFilters` - [**Deprecated** - replaced by `skipClasses`] Skip the specified classes when stepping. Class names should be fully qualified. Wildcard is supported.
- `skipClasses` - Skip the specified classes when stepping.
- `$JDK` - Skip the JDK classes from the default system bootstrap classpath, such as rt.jar, jrt-fs.jar.
- `$Libraries` - Skip the classes from application libraries, such as Maven, Gradle dependencies.
- `java.*` - Skip the specified classes. Wildcard is supported.
- `java.lang.ClassLoader` - Skip the classloaders.
- `skipSynthetics` - Skip synthetic methods when stepping.
- `skipStaticInitializers` - Skip static initializer methods when stepping.
- `skipConstructors` - Skip constructor methods when stepping.
### User Settings
- `java.debug.logLevel`: minimum level of debugger logs that are sent to IDE, defaults to `warn`.
- `java.debug.settings.showHex`: show numbers in hex format in "Variables" viewlet, defaults to `false`.
- `java.debug.settings.showStaticVariables`: show static variables in "Variables" viewlet, defaults to `false`.
- `java.debug.settings.showQualifiedNames`: show fully qualified class names in "Variables" viewlet, defaults to `false`.
- `java.debug.settings.showLogicalStructure`: show the logical structure for the Collection and Map classes in "Variables" viewlet, defaults to `true`.
- `java.debug.settings.showToString`: show 'toString()' value for all classes that override 'toString' method in "Variables" viewlet, defaults to `true`.
- `java.debug.settings.maxStringLength`: the maximum length of string displayed in "Variables" or "Debug Console" viewlet, the string longer than this length will be trimmed, defaults to `0` which means no trim is performed.
- `java.debug.settings.numericPrecision`: the precision when formatting doubles in "Variables" or "Debug Console" viewlet.
- `java.debug.settings.hotCodeReplace`: Reload the changed Java classes during debugging, defaults to `manual`. Make sure `java.autobuild.enabled` is not disabled for Java(Support OpenJDK11) extension.
- `manual` - Click the toolbar to apply the changes.
- `auto` - Automatically apply the changes after compilation.
- `never` - Never apply the changes.
- `java.debug.settings.enableRunDebugCodeLens`: enable the code lens provider for the run and debug buttons over main entry points, defaults to `true`.
- `java.debug.settings.forceBuildBeforeLaunch`: force building the workspace before launching java program, defaults to `true`.
- `java.debug.settings.onBuildFailureProceed`: Force to proceed when build fails, defaults to false.
- `java.debug.settings.console`: The specified console to launch Java program, defaults to `integratedTerminal`. If you want to customize the console for a specific debug session, please modify the 'console' config in launch.json.
- `internalConsole` - IDE debug console (input stream not supported).
- `integratedTerminal` - IDE integrated terminal.
- `externalTerminal` - External terminal that can be configured in user settings.
- `java.debug.settings.exceptionBreakpoint.skipClasses`: Skip the specified classes when breaking on exception.
- `$JDK` - Skip the JDK classes from the default system bootstrap classpath, such as rt.jar, jrt-fs.jar.
- `$Libraries` - Skip the classes from application libraries, such as Maven, Gradle dependencies.
- `java.*` - Skip the specified classes. Wildcard is supported.
- `java.lang.ClassLoader` - Skip the classloaders.
- `java.debug.settings.stepping.skipClasses`: Skip the specified classes when stepping.
- `$JDK` - Skip the JDK classes from the default system bootstrap classpath, such as rt.jar, jrt-fs.jar.
- `$Libraries` - Skip the classes from application libraries, such as Maven, Gradle dependencies.
- `java.*` - Skip the specified classes. Wildcard is supported.
- `java.lang.ClassLoader` - Skip the classloaders.
- `java.debug.settings.stepping.skipSynthetics`: Skip synthetic methods when stepping.
- `java.debug.settings.stepping.skipStaticInitializers`: Skip static initializer methods when stepping.
- `java.debug.settings.stepping.skipConstructors`: Skip constructor methods when stepping.
- `java.debug.settings.jdwp.limitOfVariablesPerJdwpRequest`: The maximum number of variables or fields that can be requested in one JDWP request. The higher the value, the less frequently debuggee will be requested when expanding the variable view. Also a large number can cause JDWP request timeout. Defaults to 100.
- `java.debug.settings.jdwp.requestTimeout`: The timeout (ms) of JDWP request when the debugger communicates with the target JVM. Defaults to 3000.
- `java.debug.settings.jdwp.async`: Experimental: Controls whether the debugger is allowed to send JDWP commands asynchronously. Async mode can improve remote debugging response speed on high-latency networks. Defaults to `auto`, and automatically enable async mode in IDE - Insiders.
- `auto` (Default)
- `on`
- `off`
- `java.debug.settings.vmArgs`: The default VM arguments to launch the Java program. Eg. Use '-Xmx1G -ea' to increase the heap size to 1GB and enable assertions. If you want to customize the VM arguments for a specific debug session, please modify the 'vmArgs' config in launch.json.
- `java.silentNotification`: Controls whether notifications can be used to report progress. If true, use status bar to report progress instead. Defaults to `false`.
> Pro Tip: The documentation [Configuration.md](https://gitee.com/openkylin/vscode-java-debug/blob/master/Configuration.md) provides lots of samples to demonstrate how to use these debug configurations, recommend to take a look.
## Feedback and Questions
You can find the full list of issues at [Issue Tracker](https://gitee.com/openkylin/vscode-java-debug/issues).

View File

@ -1,7 +1,7 @@
{
"name": "vscode-java-debug",
"displayName": "Kylin Java Debug (Support openjdk11 runtime)",
"description": " Fork of vscode-java-debug ,a lightweight Java debugger",
"displayName": "Kylin Java Debug (Support OpenJDK11)",
"description": " Fork of vscode-java-debug,modified on the lower version to support OpenJDK 11,a lightweight Java debugger",
"version": "0.1.8",
"publisher": "KylinIDETeam",
"aiKey": "67d4461e-ccba-418e-8082-1bd0acfe8516",