l0ng-ai ee5d912157 fix(java): run Application and Spring Boot configs from the project root (#1475) ...

Configurations created for a main class, and the Spring Boot applications
detected in a module, set their working directory to the module directory.
A relative path in the VM options (such as --module-path=app/server/target/dependency)
then resolved against the module and the JVM failed to start. They now leave the
working directory empty, so the process starts in the project root, which is what
an empty working directory means elsewhere. The module is still stored separately
and keeps supplying the classpath and the debugger's sources.

Fixes #1197

2026-11-05 13:55:34 +08:00

..

config.rs

fix(java): resolve application classpaths independently of working directory (#493)

2026-10-31 00:59:22 +08:00

detect.rs

fix(java): run Application and Spring Boot configs from the project root (#1475)

2026-11-05 13:55:34 +08:00

dotnet.rs

feat(run): .NET project run and debug configurations (#686)

2026-11-01 19:34:31 +08:00

import_jetbrains.rs

feat(run): import the Node interpreter of JetBrains npm configurations (#1144)

2026-11-04 09:57:44 +08:00

import_vscode.rs

feat(run): import run configurations from .vscode/launch.json (#1030)

2026-11-04 00:09:38 +08:00

process.rs

feat(run): Django test configurations with results in the test tree (#869)

2026-11-02 22:49:04 +08:00

tomcat_artifact.rs

fix(tomcat): resolve the WAR artifact of the selected Maven module (#529)

2026-10-31 12:08:27 +08:00