如何配置VSCode实现Gradle/Kotlin项目的调试功能？

我正在尝试通过Devcontainer在VSCode中整合前后端开发工作流，替代原本后端用IntelliJ、前端用VSCode的模式，同时考虑使用Codespace/Gitpod，目标是简化全栈调试流程。

目前已实现Gradle项目的构建与运行，但调试功能无法正常工作，尝试了两种配置均失败：

尝试1：VSCode Gradle扩展任务配置 #

配置内容如下，服务器能正常构建运行，但调试无效：

{
    "type": "gradle",
    "id": "/workspaces/mycode/serverrunMyCode",
    "script": "run",
    "description": "Runs this project as a JVM application",
    "group": "application",
    "project": "MyCode",
    "buildFile": "/workspaces/mycode/server/build.gradle.kts",
    "rootProject": "MyCode",
    "projectFolder": "/workspaces/mycode/server",
    "workspaceFolder": "/workspaces/mycode/server",
    "args": "",
    "javaDebug": true,
    "problemMatcher": [
        "$gradle"
    ],
    "label": "Server Debug"
}

尝试2：Kotlin扩展启动配置 #

出现依赖缺失问题，配置内容：

"configurations": [
    {
        "type": "kotlin",
        "request": "launch",
        "name": "Kotlin Launch",
        "projectRoot": "${workspaceFolder}",
        "mainClass": "io.mycode.ServerKt"
    }
]

错误信息：

[INFO] main      Connected to client
[INFO] async1    Resolving dependencies for 'server' through Gradle's CLI using tasks [kotlinLSPProjectDeps]...
[WARN] async1    Could not resolve classpath using Gradle: ClassLoader.getSystemResourceAsStream(scriptName) must not be null
[INFO] async1    Could not resolve kotlin-stdlib using Maven: Cannot invoke "java.nio.file.Path.getFileSystem()" because "path" is null
[INFO] async1    Successfully resolved kotlin-stdlib using Gradle
[INFO] async1    Starting JVM debug session with main class io.mycode.ServerKt
Error: Unable to initialize main class io.mycode.ServerKt
Caused by: java.lang.NoClassDefFoundError: mu/KLogger
[INFO] eventBus  Sent exit event
[INFO] async0    Exiting JDI session

核心问题：在VSCode中实现Gradle/Kotlin项目（含调试功能）的可行配置方案是什么？

方案1：优化Gradle扩展的调试配置 #

Gradle扩展的javaDebug参数需配合调试端口映射使用，调整后的配置如下：

1. 简化.vscode/tasks.json中的Gradle任务配置，添加调试启动参数：

{
    "version": "2.0.0",
    "tasks": [
        {
            "type": "gradle",
            "script": "run",
            "project": "MyCode",
            "javaDebug": true,
            "args": "--debug-jvm",
            "label": "Server Debug"
        }
    ]
}

--debug-jvm参数会强制Gradle在启动JVM时开启调试模式，默认监听5005端口。

2. 在.vscode/launch.json中添加附加调试配置，连接到Gradle启动的调试端口：

{
    "version": "0.2.0",
    "configurations": [
        {
            "type": "java",
            "name": "Attach to Gradle Debug",
            "request": "attach",
            "hostName": "localhost",
            "port": 5005,
            "projectName": "MyCode"
        }
    ]
}

使用步骤：

• 先运行Server Debug任务，此时应用会暂停等待调试器连接
• 再启动Attach to Gradle Debug调试配置，即可正常断点调试

方案2：直接使用Java Debugger结合Gradle构建产物 #

绕过Kotlin扩展的依赖解析问题，直接基于Gradle构建的产物启动调试：

1. 先执行Gradle构建生成完整运行资源：

./gradlew :server:build --no-daemon

也可在VSCode的Gradle面板中执行server > Tasks > build。

2. 在.vscode/launch.json中配置Java调试器，指定主类和classpath：

{
    "version": "0.2.0",
    "configurations": [
        {
            "type": "java",
            "request": "launch",
            "name": "Launch Kotlin Server",
            "mainClass": "io.mycode.ServerKt",
            "classpath": "${workspaceFolder}/server/build/classes/kotlin/main:${workspaceFolder}/server/build/libs/*.jar:${workspaceFolder}/server/build/dependency-libs/*",
            "projectName": "MyCode"
        }
    ]
}

若项目依赖路径复杂，可先执行./gradlew :server:dependencies确认路径，或添加Gradle任务将依赖统一复制到指定目录：

// 在server/build.gradle.kts中添加
tasks.register<Copy>("copyDependencies") {
    from(configurations.runtimeClasspath)
    into("build/dependency-libs")
}

执行./gradlew :server:copyDependencies后再配置classpath。

方案3：修复Kotlin扩展的依赖解析问题 #

针对尝试2中的NoClassDefFoundError，按以下步骤修复：

1. 在server/build.gradle.kts中确保依赖完整（以kotlin-logging为例）：

dependencies {
    implementation("org.jetbrains.kotlin:kotlin-stdlib-jdk8")
    implementation("io.github.microutils:kotlin-logging-jvm:3.0.5")
    // 其他项目依赖...
}

2. 刷新Gradle依赖：

./gradlew :server:refreshDependencies

3. 修改Kotlin扩展启动配置，使用Gradle扩展自动获取classpath：

{
    "type": "kotlin",
    "request": "launch",
    "name": "Kotlin Launch",
    "projectRoot": "${workspaceFolder}/server",
    "mainClass": "io.mycode.ServerKt",
    "classpath": "${command:gradle.getClasspath}"
}

${command:gradle.getClasspath}会调用Gradle扩展获取正确的项目classpath，避免手动配置错误。

额外注意事项 #

• Devcontainer/Codespace/Gitpod中需预装必要扩展：Gradle for Java、Debugger for Java、Kotlin，可在.devcontainer/devcontainer.json中配置：

"extensions": [
    "vscjava.vscode-java-pack",
    "gradle.gradle",
    "fwcd.kotlin"
]

• 调试前执行./gradlew clean build，确保构建产物为最新版本

内容的提问来源于stack exchange，提问作者ygini