Repository navigation
Error: Could not find or load main class @x.y.z.argfile #769
Description
[provide a description of the issue]
Environment
- Operating System: MacOS 10.14.6
- JDK version: 1.8.0_151
- Visual Studio Code version: 1.42.1
- Java extension version: Extension Pack 0.8.1
- Java Debugger extension version: I can't figure out how to determine this: "debugger for Java" doesn't appear in list of installed extension
Steps To Reproduce
-
[step 1]
-
[step 2]
The issue is that upon launching a debugger, VS Code runs this command line:
~/Sync/projects/music/music-03:cd /Users/Mike/Sync/projects/music/music-03 ; /Library
/Java/JavaVirtualMachines/jdk1.8.0_151.jdk/Contents/Home/bin/java
-agentlib:jdwp=transport=dt_socket,server=n,suspend=y,address=localhost:58363
-Dfile.encoding=UTF-8 @/var/folders/pn/3p41p2fj14d50n707c7x2p4c0000gn
/T/cp_90sfb6m3zinsbhwyvyknqb5hv.argfile ptcs.App
And I get this error:
Error: Could not find or load main class
@.var.folders.pn.3p41p2fj14d50n707c7x2p4c0000gn.T.cp_90sfb6m3zinsbhwyvyknqb5hv.argfile
I have no idea where the command line came from... as far as I can tell, it's illegal on Mac to use an "at sign" @ in the command line, and java is trying to interpret that as the main class, so something is wrong.
[attach a sample project reproducing the error]
attach logs
Create Maven project in VS Code... install all Java extensions.
Work with project for several months, making many changes. Not sure what details are significant.
Here's the project:
music-03.zip
Try to launch debugger in maven project, using the default launch.json. I'm not using the "current file" one, but using the (Launch) - App config.
"version": "0.2.0",
"configurations": [
{
"type": "java",
"name": "Debug (Launch) - Current File",
"request": "launch",
"mainClass": "${file}"
},
{
"type": "java",
"name": "Debug (Launch)-App",
"request": "launch",
"mainClass": "ptcs.App",
"projectName": "music-03"
}
]
Activity
testforstephen commentedon Mar 2, 2020
@argfile is only supported by java 9 and above, this looks like the debugger uses a wrong approach to shorten the command line.
There are two workarounds to unblock you first:
The first one is to add
"shortenCommandLine": "jarmanifest"to your launch.json.The second one is to change your JAVA_HOME environment variable to /Library
/Java/JavaVirtualMachines/jdk1.8.0_151.jdk/Contents/Home, and close vscode and reopen it again.
dgh1000 commentedon Mar 3, 2020
Thanks, that works. Would updating my project to Java 11 work as well? I just gave it a try and it that also seems to work without needing your other proposals.
testforstephen commentedon Mar 3, 2020
CORRECT! You don't need the additional workaround if you update the project to Java 11.
dgh1000 commentedon Mar 3, 2020
Okay you can close this (or should I? not sure how this works)
testforstephen commentedon Mar 3, 2020
it still has space to improve in the debugger side, let's keep it open first. i'm trying to deliver some enhancement in the debugger.
testforstephen commentedon Mar 4, 2020
User's JAVA_HOME points to JDK 11, his project is Java 8. The debugger will use JDK 8 to launch his application. But the debugger uses a wrong approach @argfile to shorten the command line for the JDK 8.
Cause:
Debugger 0.25.0 version adds a fix to choose the project's Java runtime to launch the application instead of the JAVA_HOME. On the other side, when the debugger computes the approach of shortening the command line length, it still uses the JDK from JAVA_HOME to check the compatibility, where it's supposed to use the project's Java runtime as the checker.
[-]running debugger in Maven project produces command with illegal @ symbol[/-][+]Error: Could not find or load main class @x.y.z.argfile[/+]